Tag: update

Spin Rewriter API keys system updated

We just rolled out another “silent” update to the Spin Rewriter API infrastructure.

What I mean by “silent” is that you’ll hopefully never notice that we even rolled it out. Unless you need one of its new benefits, that is. The new “API keys” system makes it possible to revoke or change API keys for existing users which will prove to be very helpful in the long run.

For example, if you were recording a promotional video about Spin Rewriter for your users and you unintentionally revealed your API key in the video, there’s nothing to worry about anymore. You can just contact our support desk and they’ll revoke your old API key (because it’s now publicly known) and re-issue you a new one.

Onwards and upwards with awesome behind-the-scenes updates! 😉

Smooth sailin’

Phew,

It’s always quite stressful whenever we’re tweaking any particular bit of our server network… Let alone completely revamping our infrastructure, upgrading every server in the process, and rolling out HTTPS (SSL) at the same time!

But now, after 2 full weeks, I can confidently say that our server infrastructure upgrade has been a resounding success all-around!

It’s been smooth sailing for 14 straight days now, without even a hint of issues or down-time, and our users are reporting an even better user experience than before. And that’s always a huge success in our book!

 

Biggest server upgrade ever is looking GOOD!

As mentioned in my post from August 5th (and my other post from August 7th) we’ve just rolled out the biggest server infrastructure upgrade EVER in the entire history of Spin Rewriter.

We started moving all data over to the new infrastructure at 11:42 AM EDT today. The first instance of downtime occurred at 11:48 EDT and lasted 6 minutes. The second (and last) instance of downtime occurred at 1:22 PM EDT and lasted 14 minutes.

When all our websites became available once again at 1:36 PM EDT, the spinning functionality of Spin Rewriter took an additional 26 minutes to fully reboot.

Since 2:02 PM EDT all of our systems have been up & running, and running better than ever before! 😀

As an added bonus, we also switched the entire Spin Rewriter website over to the HTTPS protocol with an SSL certificate today, for added security and reliability.

This means you can update your bookmarks to https://www.SpinRewriter.com 😀

Bottom line, I hope you’re going to LOVE this new, snappier, even more robust Spin Rewriter! 😉

< Part 1: We’re working on the biggest server upgrade EVER
< Part 2: Our biggest server upgrade ever just became even BIGGER

Our biggest server upgrade ever just became even BIGGER

I already told you a little bit about our upcoming humongous server upgrade two days ago, on Wednesday… and I’m super happy to say that the upgrade is coming along very nicely, indeed!

We’ve settled on the final configuration of our new servers and we’ve already rolled out a parallel grid of brand-new servers with an identical copy of Spin Rewriter so we can work on the copy without disturbing anyone on the actual “live” website. Right now we’re in the testing stage and I believe we’ve already squashed most of the bugs that felt like making an appearance after the huge server migration.

In other words, we’re progressing quite nicely! So nicely, in fact, that we’ve decided to go a step further than planned while still sticking to our original timeframe. With the finalized server upgrade next week we’re now also planning to roll out SSL support, in other words that green “https” version of the Spin Rewriter website for extra security and reliability.

We’re very excited about this (as you can probably tell), and will keep you posted! 😉

> Part 3: Biggest server upgrade ever is looking GOOD!

We’re working on the biggest server upgrade EVER

In preparation for the upcoming Spin Rewriter 6.0 launch (which is going to be HUGE!) we’re also working on our server infrastructure.

Right now we’ve got the biggest server infrastructure upgrade on our hands that we’ve EVER rolled out, and while it’s been quite a stressful couple of weeks this upgrade is only going to make Spin Rewriter better. And we want only the best for you guys.

We’re expecting to roll out the brand-new server infrastructure some time during next week, i.e. probably between Monday, August 10th and Friday, August 14th. At the moment we’re still performing the final tweaks and selecting the most suitable versions for a couple of our sub-component systems to ensure the best possible experience for our users.

If all goes well, there shouldn’t be more than 25-30 minutes of down-time when we roll out the upgrade. Of course we’ll also let you know about the upgrade in advance in order to minimize the impact on your effective work.

Hopefully you’ll notice when your entire Spin Rewriter experience becomes even snappier. 😉

> Part 2: Our biggest server upgrade ever just became even BIGGER

Improved UI responsiveness

We’ve just finished working on some behind-the-scenes programming black-magic which is going to speed up the User Interface of Spin Rewriter quite significantly, which means it will improve the existing User Experience in its entirety.

We used some clever bits of caching in strategic places, and made sure that our servers are always working on the stuff with the highest priority to ensure your page loads are as instant as possible. Average article processing time is also down almost 12% which is quite a big deal considering how incredibly optimized most of our infrastructure already is.

We hope you like these new updates!

Minor bugfixes

We just pushed out an update that fixed a couple of (very) minor bugs that have crept up during our very active development phase over the last couple of weeks.

One example of such bug was the situation where Spin Rewriter’s been processing all HTML code 100% flawlessly with one very uncommon exception. Whenever it was processing HTML links, it was expecting those links to contain the href attribute because that’s basically a required attribute for links to actually work. The href attribute tells a link where to take the person who clicks it. For example:

<a href=”http://www.example.com”>This is a link.</a>

Clicking this link will take you to the example URL inside the href attribute. Makes sense, right?

Well, there are some use-cases where a programmer would use HTML links without the href attribute, like this for example:

<a class=”sampleLinkClass”>This is also a link but it doesn’t point anywhere.</a>

As you can see, this link doesn’t have a href attribute at all. And whenever Spin Rewriter came across one of these *weird* links, it got a little bit confused and forgot to put back the “<a” part of the link when it was done spinning the text inside of it. Oops.

Well, it’s all fixed now and Spin Rewriter is now even more robust than ever before!