As you might’ve noticed, Spin Rewriter has been using an SSL certificate for about a year now — which allows us to serve the entire website and all parts of Spin Rewriter’s user interface securely over the “https” protocol to all of our customers.
This means no one can intercept any of your traffic, including your username or password, the articles you’re spinning, or learn anything else about your activity on the Spin Rewriter website at all. We think that’s pretty cool — and it’s definitely the right way to do things when it comes to running an online business.
Well, our SSL pilot project has been extremely well received and didn’t introduce any glitches to our systems whatsoever — so we’ve now decided to go all-in with SSL support and have just extended our SSL certificate for another 3 years.
While we were at it, we also performed a security audit of the entire Spin Rewriter website plus all of our back-end systems including our API… and I’m super happy to report that we’ve passed all security tests with flying colors. 😀
Bottom line: This means you’re in good hands, and we’ll make sure we keep it that way. 😉
Once again we’ve been focusing our efforts on the official Spin Rewriter WordPress Plugin — and as a result, we’re super happy to announce that we’ve just rolled out a brand new version of it.
This new version is called “version 2.5” (very imaginative, we know!) and it ensures full compatibility with the newest version of the WordPress platform, “WordPress 4.5.2 Coleman”. It also brings a number of minor usability tweaks and stability improvements to the already-rock-solid Spin Rewriter WordPress Plugin.
Feel free to update your Spin Rewriter WordPress Plugin to the newest version right away as it’s already available inside your account. Of course you’ll keep all of your settings and projects after the update, the update is completely free of charge and it’s definitely recommended. Enjoy! 😉
In my previous post I already mentioned how we’re rolling out some minor tweaks and fixes for various edge-cases when it comes to automated processing of original texts before our ENL Semantic Spinning algorithms begin their work.
Now, in some extreme cases our processing algorithm could sometimes get confused when it encountered the “<” sign because it thought that maybe it signifies the beginning of an HTML tag. All HTML tags begin with “<” and then usually end with either “/>” or another “>” immediately after the name of the tag.
Here’s an example of what used to cause a problem for our parser:
Mathematicians sometimes use p < 0.01% to signify low risk.
This would in some cases (depending on the context) turn into:
Mathematicians sometimes use p (the rest of the sentence is missing)
…after the Step 1 processing because our parser mistakenly took the “< 0.01%” as a malformed HTML tag instead of what it truly was.
Well, it certainly doesn’t do that anymore — we just fixed this issue, and rolled the update out to our production servers! 😀
We’ve just rolled out another tweak to our algorithm, namely the part of the algorithm that takes you from Step 1 to Step 2 of the spinning process inside Spin Rewriter.
There used to be some edge cases where our algorithm would incorrectly place a period (.) at the end of paragraphs if the paragraph in question ended with either a single quote or a double quote, preceeded by another period.
Here’s what I mean:
This right here is a “test.” (end of paragraph)
…would sometimes turn into…
This right here is a “test.”. (end of paragraph)
…after the Step 1 processing, and you would find that additional period once taken to Step 2.
Mildly annoying, for sure. 😀 Well, not anymore — we just fixed that, and rolled out the update to our live servers! 😉
As I’ve already mentioned in my previous Redis-related post, we’re improving the data-related structure of our back-end algorithms in order to deliver even more efficient, faster ENL Semantic Spinning to our awesome Spin Rewriter users.
This time around we’ve rolled out an update to the structure of our regular SQL databases. This update has significantly reduced the size of some of the database tables (in some cases, the improvement has been as high as 64-65% which is astonishing) which resulted in much faster database queries…
…which once again translates into a faster & better user experience, and a more robust platform!
Once again we’ve improved our core infrastructure a bit which resulted in an even faster user experience for our awesome Spin Rewriter users, plus our back-end systems are now even more robust as an added benefit.
We’ve upgraded some of the more CPU-intensive algorithms so that they no longer rely on regular SQL databases. They’re now able to take advantage of the full power of Redis. So, what’s that? Here’s what their official website says about Redis:
“Redis is an open source (BSD licensed), in-memory data structure store, used as database, cache and message broker. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability via Redis Sentinel and automatic partitioning with Redis Cluster.”
I realize this sounds like a bunch of gibberish, but here’s what it really means.
Basically, Redis takes certain types of data operations and performs them in a much, much more effective way than your regular SQL database. This results in a significant speed-up of CPU-intensive algorithms such as Spin Rewriter’s incredibly advanced ENL Semantic Spinning technology.
Hope you’re loving the even faster, improved Spin Rewriter! 😉
We know that sometimes you might wish to change your Spin Rewriter API key.
Maybe you were recording a demo video with your API key clearly visible (like the video that I’ve included below!) and you want to prevent other people from abusing your API key now that they’ve seen it. No matter what your reasons are, from now on you can always easily request a brand new API key in seconds.
To do that, simply log into your Spin Rewriter account, click the “API” link at the top to be taken to the page with your current API key, and then click the “Change your unique API key” link right below your current API key.
Doing this will invalidate your old API key instantly and generate a brand new API key for you in seconds.
Or, you can watch this video that shows you how easy it is:
As you probably already know, Spin Rewriter comes with an awesome WordPress integration. Among other things, our users are able to quickly send new spun posts directly to their WordPress websites and publish those posts (remotely, from right within their Spin Rewriter account) with a single click.
We’ve now streamlined this process even further. One user-experience challenge that we were facing was, how to automatically determine the best possible title for each freshly generated WordPress post. We’ve now settled on the following:
Imagine our user (let’s call her Catherine) has just finished spinning an article within her Spin Rewriter account, and she’s ready to publish it remotely to her WordPress website with a single click. Her article looks like this:
“Learn to Play Electric Guitar – and Become a Rock God!
It’s not too difficult to learn your first couple of songs on a guitar. Here’s what you need to do: (rest of the article)”
Our WordPress integration will now automatically determine that “Learn to Play Electric Guitar – and Become a Rock God!” can be used as an awesome post title, and the rest of Catherine’s article will be used as the post body. Which is perfect.
However, imagine if Catherine’s freshly spun article didn’t come with such a clear-cut candidate for a good title. In that case, Spin Rewriter will now do its “semantic-analysis” magic and determine another great title that can be used for her WordPress post. And if it’s not able to simply use the first paragraph as the title, it will of course include the entire spun article as the post body so nothing gets lost.
OK, we’re back!
As I mentioned in the previous post (published on February 9th), here at Spin Rewriter we always strive to further improve our server infrastructure and fine-tune our code. We’re looking to deliver faster and better software that’s more intuitive and more robust than ever before.
We’ve now taken advantage of some new opportunities to parallelize certain aspects of Spin Rewriter’s existing spinning process. This means that we’re now able to run certain parts of the spinning process on multiple processors (CPUs) on different servers at the same time instead of running it on just one server.
Here’s a simplified explanation of the benefits this brings. Imagine you have an article with 20 sentences. We can either have our software detect the parts-of-speech on each of those sentences in a row, and if it takes our software one second to analyze every sentence, we’re looking at 20 x 1 second = 20 seconds of waiting time for the user.
We can, however, break this article down into 20 separate sentences — and send each of these sentences to a different server in our grid at the same time. Each of those 20 servers then processes just one sentence, and only 1 second later we get the processed results back to the central system.
The result: The same article is now fully processed in just 1 second instead of 20.
And the result that matters much more than that: Our users are even happier! 😀
Of course the exact real-world situation isn’t as cut and dry, but we were still able to roll out a significant improvement in speed and robustness of our spinning systems — and we hope you’ll love it!
OK, the title of this post might sound a bit “high and mighty”, but hopefully it shouldn’t be too difficult to understand once we break it down a bit.
As you probably already know, our server infrastructure is quite state-of-the-art which allows Spin Rewriter to have great uptime and to always process all of your articles, find the best synonyms, manipulate sentence structures, export thousands of text files etc. etc. in a matter of seconds.
We always strive to further improve our infrastructure and our back-end software code. Faster, better, more intuitive, more robust — this is what drives us.
We’ve recently dug extra deeply into our software and found some new opportunities to parallelize some aspects of the spinning process. In other words, we’re now able to run a certain aspect of the spinning process on multiple processors (CPUs) on different servers at the same time instead of running it on just one server.
We’ll bring you more details in our next post, however right now we can already give you a hint that GREAT things are underway. Stay tuned! 😉
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- January 2014
- December 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
I mostly write about:
Who is Aaron?
I'm a guy who started his own successful online business back in 2007. I was lucky enough to see my business expand 300+% every year.
At the moment my team and I reach over a million unique customers each month and always do our best to deliver the best quality services.