Wed Aug 30, 2017 11:58 pm
Hi to all,
I've got TWO important announcements for you today...
Yesterday, some eagle-eyed SBIers asked if "something was going on with SBI!?"
We had some reports of slowness while using SBI!, and problems logging in. One wondered if this was related to HTTPS -- nope, it's deeper and more long term than that...
... in a good way!
We've been making some important investments in infrastructure, including new servers and other "stuff" (my eyes glaze over -- all I know is that it's expensive as heck).
Anyway, breaking it all in, setting up and configuring and what-not is done and we're now rolling out. So...
You MIGHT have had logging in or speed issues, but the Dev team just gave us the "all clear" for the currently deployed improvements (more are in the works).
The team came up with a few ways to make SBI! work even faster for you. I don't mean faster than yesterday's slow - just FASSSS⏩⏩⏩ TTT, period!
Several of the load times are very noticeably faster now. The most noticeable changes are in the heaviest loads, which means Content 2.0 for many.
The screen for editing an existing submission loads in just a couple of seconds. The typical C2 library will load in a few seconds. Site Central should be a little quicker.
If you have dozens or hundreds of C2 invitations, it may take a few more seconds to load the entire library, but you'll notice that's a lot better than before, too!
Approving and saving a new submission still takes longer. That's due to the process involved in adding it to the database, but even that process is faster.
We often do upgrades without telling you. This one, though, is larger. And I have to admit that it's not just to save you seconds here and there.
We regularly upgrade our hardware for the same reasons that you do with your PCs and phones. Better, faster, more capacity, security, and mostly...
Our sysadmins whine that they just "WANT IT"...
If you have kids you know what I mean. Or if you have an iPhone but can't wait for September's new releases, you REALLY know what I mean! 😂 😂 😂
If you notice any quirkiness after all this work, please contact Support, providing the steps you took to arrive at the quirk.
One more time, just to be sure...
If you have trouble logging in, please report it to Support. Ditto if things seem slower.
H.E. will let you know when we've finished rolling out AND when our planned speed enhancements are all done.
That should be by end of week, but you never know, so I never promise. That keeps me out of trouble with everyone, both you and our (happy) pocket-protector propellor-heads.🤓 🤓 🤓
We've been talking HTTPS recently. Here are the threads, in chronological order (per first post)...
Google favors secure sites https - What does this mean for SBI
HTTPS Is Coming (With Some Prep Tasks for You Now)
Google Chrome Email Warning
It's optional background reading.
Meanwhile, back at the farm...
Work continues on the HTTPS conversion tester, which will be released very soon, and the tool for the conversion to HTTPS, which will be available no later than __________.
I don't "do dates" (and I'm not talking about the kind that Janice would be waiting for me with a shotgun in her lap).
The Dev team doesn't like it when I give release dates, since it raises your expectations and puts pressure on them. And the fact is... stuff happens.
This one, though, is a "hard" release date because of the Google Chrome deadline in October. We want to beat that comfortably.
So they gave me the OK on this one! It's October 1 (or a few days later). No matter what, we'll beat Chrome.
A Bit of General Background
As you know, we watch important shifts in the Internet carefully. Google has spearheaded this push/"extortion," but there have been other projects of theirs that did not come to pass due to lack of uptake.
So we sometimes employ watchful waiting.
Our "adoption timing" varies according to what's involved. For example...
- We bought into Google's sitemap.xml concept immediately. We were first out with an automated tool that took you zero time.
- We waited until Google announced which type of mobile pages it preferred and then took that direction. We had previously ignored .mobi, which everyone was calling the next big thing for mobile. We couldn't believe that most mid-sized companies, let alone solopreneurs, would create an entirely different 2nd site for mobile. Some did, but not nearly enough to create a new "standard."
- And for this one...
In normal times, this push would likely have failed (or at least taken much longer to be adopted). But security is a big, frantic issue nowadays. How crazed is it? Ultimately (not this year, likely), even harmless content sites will be flagged as non-secure.
The irony is that there's not a ton of benefit. HUMANS remain the weak link and hacks will continue unabated. But I digress..
We started the planning and light prep a couple of months ago. As the adoption level passed 39% and approached 40% (which was our "GO" milestone), we pulled the trigger.
For those of you who stay "strictly kosher" when using SBI! (and I'm not talking about kitchens ), there won't be much for you to do manually. We're automating as much as possible. Even AdSense, I learned today, is reliable enough for us to convert for you -- so we're doing that, too.
That's another reason for holding back on making this type of decision. Third-parties have to offer easy ways for you to integrate them into your secure sites. More and more of them are now making it easier for you.
That reduces YOUR work load, not to mention room for error, tremendously.
So those who K-I-S-S should find this pretty simple.
If you're more adventurous with coding and go "out of the pocket" (🏈 football season, so no basketball puns for a while!), there'll be some manual work for you.
Our goal for this project is to minimize the amount of time this will take you, as well as cut the risk of traffic loss to as near-zero as possible.
We monitor stuff like this to answer the what, which, when, why and how of integrating into SBI!, minimizing or eliminating work for you. I think we've sliced this just right.
Now, about that manual work...
The first part of the module tests your site with a button click. It delivers a testing report of what you need to do.
Help Elf is working on an in-depth help file to go with the tester, so that you'll know how to resolve any issue you'll find in the testing report
The goal is to help you complete the pre-conversion tasks before the conversion tool becomes available. And then, once ready...
When you click on the "switcheroo" button (I think the name will change ), all that's left for you to do is the post-conversion tasks (the ones you need an HTTPS URL to complete).
OK, that's the announcements for this week. Infrastructure and https aren't sexy, I know. But getting the "meat and potatoes" right is important, too!
All the best,
P.S. Forget any SEO advantage promised by Google. I don't believe there ever would have been any for pure content sites. But now that most will be secure, ALL will get the benefit of some teeny factor. And when all benefit, none do.
Google can be fiendishly clever.