Notably, the report cited an 8.9% increase in statewide housing prices (measured from Q1 2013 to Q1 2014), a 3.1% bump in payroll jobs (June 2014 vs. June 2013) and a higher-than average growth in the state’s working-age population.
Ahead of Florida in Business Insider’s rankings: Colorado, California, Texas, Arizona, and Utah.
The team responsible for the report, which was published August 4, 2014, posted separately about their methodologies.
We’ve all known since that fateful Tuesday in 2001 that Sarasota had a connection to the events of the day we call 9/11. I’ve written previously about being held up by the Presidential motorcade as “W” made his way to Emma E. Booker Elementary school to read to the kids. Then there was the flight school in Venice where some of the “I don’t need to know how to land” hijackers trained.
Much later, we learned some bits and pieces about the Sarasota Saudis, and—perhaps the most concerning detail—that the FBI was playing cat and mouse about what it did and didn’t know.
On Monday of this week, though, a new set of documents emerged—documents that the FBI had previously failed to acknowledge even existed—that reveal even more bizarre details about the 9/11 Sarasota connection and what appears to be an FBI coverup.
Thanks to some extremely diligent efforts on the part of the Broward Bulldog and their ongoing investigative and legal actions, the FBI released the documents which, although heavily redacted, reveal information uncovered as far back as 2002.
An article published by the Broward Bulldog and picked up by the Miami Herald reveals the new details. They include a man dumping information into a dumpster behind a Bradenton storage facility, and a man who arrived in Sarasota, FL in November, 2001 harboring apparent intentions to purchase land and establish a Muslim compound in Florida that was (is?) feared to include carrying out or facilitating terrorist activities.
A while back, my treasured Starbucks “Barista” Burr Grinder suffered a nasty fall. It’s a long story. Not my best day.
The grinder itself was just fine, but the coffee bean hopper that sits atop the grinder didn’t fare so well. The “business end” of the hopper was ruined. I call it the business end because without the hopper installed, the grinder won’t run for safety reasons. It also is used to set the coarseness of your grind.
Locating a New Hopper
This should be no problem, right? I’ll just search Google for “starbucks barista grinder hopper” right?
It turns out that Starbucks has sold a few different private label grinders wearing the “Barista” moniker. There were a number of results in Google that made me think I’d have no problem finding parts for my grinder. Unfortunately, though, it became clear pretty quickly from the photos on the sites that my grinder wasn’t the one they were selling parts for.
In the end, I turned the grinder over and located this sticker, which told me that I have the “EL 60″ burr grinder specifically.
While that was nice for informational purposes, it didn’t seem to be much help online when hunting for parts.
Ultimately, I decided that my grinder was manufactured by Solis, a Swiss company which offers this model which appears (from the photo, anyway) to be identical to mine. Other searches revealed that my grinder had been sold as the “Solis 166″ at one time.
Nice to know, but no parts.
After a few more rounds of Google searching, I decided that it might be worthwhile to contact Baratza, which appears to make (or at least import) the successor models to the EL 60—both for Starbucks’ “Barista” line and otherwise.
Prior to purchasing the replacement hopper from the Baratza website, I contacted their support department by filling out a form on their website.
I was very impressed with the great service I received—especially since I was only planning to spend $10 on the hopper (or, as it turned out, $14 including the lid). After inquiring as to whether or not they sold the replacement hopper I needed, I received the following via email:
Our hopper does not fit right onto the Barista. However, I did have one crafty customer modify one of our hoppers, he made a guide for doing the job. I have the guide attached- sorry it is in two parts, but the customer sent it to me already in PDF form like this.
Pierce Jens Baratza Email Support
The PDFs that were attached were somewhat helpful, but unclear in some ways, so I decided to create this post as a way to “upgrade” the available information about how to make the Baratza hopper work on the Barista EL60 / Solis 166 grinder.
I ordered the grinder right away, and added the lid as well. I had a suspicion my lid (which was intact) would fit, but I could see that the Baratza hopper was kind-of a “smoke” color, whereas mine was clear. For $4, why not get the matching lid?
Opening the package, I decided the grinders Baratza sells today indeed must share some common ancestry with my grinder, as the hoppers are exactly the same diameter at the point where they come to rest on top of the grinder.
However, the “notches” that allow the hopper to adjust the grind—not to mention get “seated” properly in place—are not where they need to be on the Baratza replacement hopper.
So… I reviewed the modifications made by the generous and helpful person who created the PDFs that Baratza sent me, and went for it.
How I Modified the Baratza Hopper to Work in My Barista Grinder
The guides Baratza sent referenced a “rotary tool” which the customer apparently used to grind new notches in the Baratza hopper to make it fit. I’m guessing it was a Dremel tool of some sort, which I don’t have.
So I read and re-read the guides and decided that an super-sharp razor blade just might do the trick.
WARNING: Razor blades are incredibly dangerous. Seriously… use every possible precaution to avoid injury if you try this. Clear the area of any bystanders or spectators, and proceed at your own risk.
I started with 2 vertical cuts on the side that didn’t have anything in the way, as shown below. By cutting straight down, no body parts were in the “line of fire” (so to speak) in the event that the razor blade were to slip.
I was quite pleasantly surprised at how easily my sharp razor blade cut through the plastic hopper. If I got a little stuck, it just took a little forward or backward motion (not enough that I’d refer to it as “sawing”) to make progress.
I took my time, and when I had two nice vertical cuts, I very carefully made a horizontal one to finish out my notch.
Once that first notch was cut, I turned the hopper around and tried to discover what needed to happen on the other side. From what I could see, my hopper was slightly different from the one pictured in the guides I received. In my case, there was a “tab” that ran all the way to the “top” (when sitting upside down as it was when I was working on it) of the hopper rim. After some tinkering, I decided that at least part of it (enough to match the height of my other notch) needed to be removed. I decided not to remove all of it because it seemed like it may have had some purpose. Honestly, I’m not sure.
Again, the razor blade really seemed like the ideal tool for the job. I worked veryslowly and kept body parts out of the way in case of slippage.
Once that was done, I cut a notch in the “rim” of the hopper just like the first one.
With both notches cut, I did a little comparison to even things out a bit, and ultimately cut both notches a bit “taller” than I had done originally. Once they seemed to match, I installed the hopper onto the grinder…
The new hopper now works just as the original one did. By rotating the hopper, the grind can be adjusted from “coarse” (with the little tab above the french press as shown in the photo above) to “fine” just as before.
And… as before, the safety cutoff switch is activated properly only when the hopper is properly installed and rotated far enough to be “locked” into place.
Thank You to Baratza and the Unknown Crafty Customer
I wouldn’t have attempted this mod if it weren’t for the fantastic service from Baratza (thank you, Pierce!) and the anonymous Baratza customer who blazed the trail and wrote up the guide to the modification he or she made.
Hopefully, this guide is helpful to you. If I can answer any questions, I’ll do my best! Just add a comment below.
With this nifty mod, I plan to enjoy my Starbucks Barista EL60 grinder for many more years. It has truly been the best grinder I’ve ever owned! And… next time I need one, I’ll be buying a grinder directly from Baratza.
There was no way to log in to the support site to post my issue… because I couldn’t log in!
So… after I responded via Twitter to that effect, I was pleasantly surprised to receive an email from Amazon support. I’m still not 100% certain how they figured it out, but they managed to locate my account and my email address just from my tweets. (I actually think I got doxxed by Amazon Support, but that’s OK!)
Ultimately, they called me as well, because I wasn’t able to get logged in to reply to the case ID that had been established for me.
As Amazon continued to work on their end, I also engaged in some troubleshooting on my own:
Tried to sign in from another browser. I normally use Chrome for my daily driver, but I tried to login from Firefox
Tried to sign in using Firefox “Private Window” to eliminate the browser cache and any cookies that might be affecting sign-in.
I actually busted out Internet Explorer (cringe!). Since this is a fairly recent install of Windows 7, I knew that I had never logged in to an Amazon account from IE, so that also gave me a fair test without the normal Amazon cookies and browser cache..
Used my wife’s laptop to try to sign in.
In every case, I received the exact same error.
One of the messages I received from AWS Support suggested that I attempt to login to another account. Although my AWS setup is all connected to my primary Amazon account, I did have another account or 2 that I could try. I was successful in logging in right away using the first account I tried.
So…. I was able to conclude that the issue was directly connected to my Amazon account and didn’t have anything to do with my browser, cookies, or cache.
Since Amazon uses an OAuth process to facilitate single-sign-on to multiple Amazon properties via a single account, I thought, “I’ll just sign in and review my Amazon order history.”
No dice. Same error.
Ultimately, after Nolan from Amazon Web Services Support got me on the phone, I walked him through all that I had done. He told me how puzzled they were on their end, since everything in my account looked OK.
He first directed me to try to log in from a couple of specific locations, just to rule out user error (I’m guessing).
After some effort, he asked if I would click the “Forgot Password” link.
“Hmmm…. why didn’t I think of that?”
I guess it hadn’t occurred to me because I was too busy ruling out all sorts of other issues.
So, I used the password reset function and created a new password. That’s when I did see a warning from Amazon’s site about cookies. I wish I had noted the actual error (or taken a screenshot of it). I didn’t. The error message seemed to indicate that my browser wasn’t accepting cookies (I was back in Chrome now, so I knew it was accepting cookies).
At this point, I decided to go ahead and remove all Amazon cookies from Chrome. Once I did, I was able to login.
Thank you, Amazon support! Thank you, Nolan!
Apparently there was some corruption with my Amazon account on Amazon’s servers. I believe this because I saw the same error from every browser I tried to use—even from multiple machines. Apparently, the process for resetting my password cleared the issue!
Bottom line: If you see this error, reset your password. You may also need to remove Amazon cookies from your browser.
P.S. I was very impressed with the security procedures at Amazon. In every communication (I also tried to get support via chat), they took multiple steps to confirm my identity before proceeding. Kudos to them for establishing solid procedures for this!
We’re kicking off a brand new feature here today on EpiphanyDigest: Sarasota Entrepreneur Profiles. We’ll be writing up local entrepreneurs who have caught our attention, and tell you why! First up: Steve Rinehart.
If you’d like to nominate someone, leave us a note in the comments below.
Those of you who know me well already know this: I’m a huge fan of entrepreneurs.
Especially the “chase your dream, innovate and adapt as necessary, and work really hard ’til you see it come about” variety.
And this is precisely why I was intrigued when I first met Steve Rinehart. It was about two and a half years ago now, and a good friend of mine was providing some entertainment in a local night club venue. He suggested that I meet up with the owner, because he had real vision but had run into some difficulties in the business.
The venue was “The Loft Ristobar,” and it was located in the building that had previously housed Sarasota’s highly popular Tex-Mex chain restaurant, Don Pablo’s.
The Loft was a concept that was either ahead of its time, or perhaps just better suited to a bigger market. But the idea, I thought, was brilliant. Restaurant by day, live entertainment venue in the evenings, and then… after hours on weekends, it transformed into a full-on night club.
But, as you might imagine, those are at least two (and possibly three) different businesses all rolled up into one. This meant that the business was surprisingly complex, with lots of areas that needed specific attention.
Creating a clear marketing message out of the three of them was what I was immediately tasked with doing. Let’s just say it wasn’t the easiest thing I’ve ever been asked to do.
And to top it all off, Rinehart Homes, Steve Rinehart’s day job, was busy and complicated enough that it demanded lots of his time and most of his attention. The management Steve had in place at The Loft did a bang-up job, but it just wasn’t enough to get the concept to really take off.
Why Not Franchise?
As Steve related to me, many times during the course of his time operating The Loft Ristobar, people would come in and ask about Don Pablo’s. Where did it go? What happened to it?
The reality was that the Sarasota store had long been one of the chain’s top-performing restaurants. But when the parent corporation ran into financial troubles, it closed all but 38 stores—the ones that were geographically easier for them to manage. A new company bought the brand and those 38 stores out of bankruptcy and they were doing OK.
The idea of coming back to Sarasota was a good one, but the company wasn’t ready to take the plunge yet as they were taking a measured approach to growth.
So Steve did what any enterprising entrepreneur would do: he seized the opportunity and negotiated the chain’s first-ever franchise deal. In May of 2012, five years or so after it had closed, Sarasota’s Don Pablo’s reopened as a franchise operation.
That business has been through its fair share of ups and downs, but today it is humming along with a great management team in place. Steve has high hopes for its future.
In the meantime… Sarasota’s real estate market had begun to pick up.
Building Custom Homes in Sarasota
Since 1994, when Steve Rinehart first obtained his Florida General Contractor’s license, he had attacked the home-building business with gusto. Not one to get stuck depending upon others, Steve went out and got his roofing license and a pool contractor’s license as well. This enabled him to be highly flexible and churn out homes at a surprising rate.
Steve’s reputation—and that of his boutique team—in that business is very good. Over the years, he and his team have built more than 300 homes that way, and provided many affordably-priced, but very nice homes for a lot of people.
But as he tells it, when the real estate market starts to heat up—especially in an intrinsically attractive market like Sarasota/Bradenton—bigger and bigger national players are willing to come in and pay far more for land than it’s worth.
That makes this business less and less attractive to a boutique team like Steve’s.
And so… the handful of higher-end projects that Steve had taken on in the last few years had started to become more and more interesting.
With a few completely custom projects on Sarasota’s Siesta Key (along with a high-end renovation or two) under his belt, Steve decided it was time to launch another new entrepreneurial venture.
With the help of 20-year veteran real estate investor Joel Match, Steve recently launched Rinehart Elite Homes. Their first project under this new name? A gorgeous home in Lakewood Ranch’s exclusive golf course community, The Concession.
As you might imagine, Steve’s life is never boring. But given his passion for excellence, his hands-on attention to detail, and the track record of satisfied home owners, I think it’s safe to say that Rinehart Elite Homes is going to be a luxury home builder to contend with.
Yesterday, I logged in via FTP to a separate hosting account on a completely different web host, and found some of the same signs that accompanied the original attack on my 1and1 account.
The first sign is a suspicious file in the root of the website. The filename is “.. ” — as in ‘dot dot space’
This is particularly insidious, because the filename is designed to make the file hard to find. This is because “..” by itself is a unix/linux standard for “parent directory.” (It’s the same way on Windows & DOS systems as well.)
Thus, if you aren’t paying attention and looking specifically for it, it’s hard to notice. Also, since most systems don’t give you any sign of the “space” in the filename, it’s hard to open the file. (Here’s where I have to give credit to a sysadmin at 1and1 for helping me discover the space in the filename. I kept telling him it was called “..” and he said, “that’s impossible.” He was right.)
Either way, I have found that you can simply rename the file and then download it via FTP to open it up and see what’s inside. Here’s the code inside the “.. ” file:
This is obfuscated somehow… perhaps encoded with base64 or some other method.
I’m not certain what it does, but my guess is that it only works when in combination with the code that was inserted into PHP files. Here are the filenames targeted by the attack:
While index.php & header.php are common filenames in a wide variety of php websites, wp-config.php is unique to WordPress. Thus, I’m fairly certain that the creators of this attack were particularly interested in attacking WordPress sites.
The wp-config.php file only shows up in the “root” folder of any given WordPress installation. On the other hand, index.php appears in a number of folders in a typical WordPress installation. Here are a few examples:
the “root” folder of the site
the wp-admin folder
the main folder of any given theme
the main folder of some plugins
The header.php file, on the other hand, is most likely to show up in one or more of your theme folders.
My guess is that whatever script gets uploaded to your server gets busy locating files that match those filenames and injecting the malicious code.
The code is intended to be hard to spot. First of all, the PHP files are edited without modifying their timestamps. Thus, they don’t look like they’ve been edited recently.
Also, the code contains an opening <?php tag, and then is immediately followed by 1183 spaces. This means that even if you open an infected file in a typical code or text editor, the malicious code will be so far off your screen that you won’t notice it. You can scroll down and see all of the untouched PHP code that you’re expecting to see in the file.
From being attacked in the past, I was already aware of both of those techniques, so I opened the files and scrolled all the way to the right, finding the code.
Here’s an exact copy of what’s being inserted into these files.
What Does This Code Do?
Well… the only reference to this particular attack that I’ve been able to find online is found in this thread (in German). That confirmed a suspicion I had held which led me to believe that there was something inserting some ad code into the WordPress admin pages (the “Dashboard” specifically) of my sites. Thus, it is only visible when logged in as an admin user, and is intentionally targeting WordPress site operators.
1and1 insisted that my sites were injecting malware into visitors’ browsers. Perhaps this is the malware. Perhaps the code was doing more than just displaying the ads I saw.
In any case, I had originally attributed these ads to a recently-added Chrome extension which I immediately disabled.
Now that I’ve seen the German thread, I’m more convinced that the sites which were displaying that ad were, in fact, the ones infected with this malicious attack.
So… I have no proof as to what this code actually does. It’s all obfuscated and it’s beyond my pay grade to figure it out anyway. My only hope is that by writing this up, someone (or perhaps more than one someone) will be able to use what I’ve discovered to help make sense out of it and put this sort of crap to an end.