Page 18 of 33

Auto Protected Keywords get API support

August 23, 2012 /

I’m sure you remember the feature we described on Monday – Spin Rewriter‘s new ability to automatically protect all capitalized keywords that appear in your articles.

Well, we’ve now rolled out this new feature to our API server as well. With this in mind, we have updated the API documentation, all of our code samples and the entire Spin Rewriter API SDK (written in PHP).

If this is all a bunch of acronyms to you, then feel free to ignore this post — however, if you’re a developer who’s using the Spin Rewriter technology through our API, you’re probably quite happy about it. 😀

Full support for tablets on the horizon

August 14, 2012 /

With the market share of tablets growing steadily and reaching new heights every month, we’re thinking of pushing out a new tablet-specific user interface that will allow all iPad, ASUS eee Pad, Samsung Tab etc. users to make the most of our technology.

While Spin Rewriter already works fine on all tablets (all functionality is supported by mobile browsers) and we have quite a number of happy iPad users, this new interface might make things even easier for tablet users. Stay tuned! 😉

Great feedback keeps on rolling in

August 2, 2012 /

We’ve been receiving a ton of great feedback and it wouldn’t be very marketing-ish of us if we didn’t post some of it on the official Spin Rewriter blog. 😉 Here goes:

“I have been looking for a service like yours for a long time and I am very happy I came across your business. Love the spin rewriter and your spin distribute services so far.”
– Carol

“hey Aaron!
i am having to tweak maybe one spintax  in ever paragraph or two and considering that it is reporting over 90% uniqueness that is really not bad at all. Keep going you are on the right path.”

We’ve also added some great new testimonals to the project’s homepage. 😀

Meet our new JV manager, Jacob

July 17, 2012 /

We’ve just had an amazing addition to our team. A young fellow named Jacob joined us, and he and I will both be talking to our JV partners and affiliates from now on.

Here’s what he has to say: “I’m very excited to be a part of the amazing Spin Rewriter team. It’s both my pleasure and a big challenge to help Spin Rewriter users get the most out of our software, to help our technicians further improve it, and to make sure all our affiliates and JV partners are as happy about the entire project as we are.”

Jacob, welcome aboard! 😀

Summer season is upon us

July 9, 2012 /

It’s been a crazy successful and more-than-mildly exhausting 6 months … 😀 … and July is the one time of the year when things usually calm down a little bit and we can breathe a bit more easily.

Our customer support department is going to be available 16 hours a day all summer long and we’ll keep on responding to all support tickets within a single business day. Our dev team (hard-working programmers) will take a short break, though, so right now our focus is on reliability of our software. We’ll be adding a new set of awesome features in September or so.

Enjoy these hot summer days, and – all the best! 😀

Spin Rewriter now recognizes even the weirdest encodings

July 2, 2012 /

You might have noticed I picked the “Programming” category for this blog post. The reason for this is quite simple – this post won’t be very interesting to 95% of you who aren’t programmers. 😉

You see, out of thousands of active users, we have received about 2-3 customer tickets each month saying that Spin Rewriter somehow garbled up the original text. We’ve been looking into this for a while now, and we found out that:

  • 99.5% of all submitted texts are processed normally
  • texts that begin with the bytecode EF BB BF are encoded in the standard UTF-8 format (works well with Spin Rewriter)
  • texts that begin with the bytecode FE FF are encoded in the UTF-16/UCS-2, little endian format (some issues)
  • texts that begin with the bytecode FF FE are encoded in the UTF-16/UCS-2, little endian format (some issues)
  • texts that begin with the bytecode FF FE 00 00 are encoded in the UTF-16/UCS-2, little endian format (sporadic issues)
  • texts that begin with the bytecode 00 00 FE FF are encoded in the UTF-16/UCS-2, little endian format (sporadic issues)

For instance, if our user entered “It іs nevеr a сonvenіent timе tо hаvе уour vеhicle quіt оn уоu.” in the UTF-16/UCS-2, little endian format, Step 2 of the spinning process appeared fine, however Step 3 showed this: “It Ñ�s nevеr a Ñ�onvenÑ�ent timе tо hаvе Ñ�our vеhicle quÑ�t оn Ñ�оu.”

We have now resolved all these issues and Spin Rewriter will process all articles that you can throw at it. 😉