Twitter is currently in the much-lambasted and disruptive process of making big changes to their API (Application Programming Interface). As the author of a WordPress plug-in which only exists with any value due to its ability to use the Twitter API, I have to be pretty attentive to these kinds of changes.
The API changes probably won’t have any significant impact on WP to Twitter or on most users of WP to Twitter. Technically, I’ve needed to change the name of the application since their last major change in terms of service – the use of the “Twitter” mark is a violation of their terms of service. (Technically, a violation of their trademark guidelines.) That will probably happen in the next few months – so be warned. It’s going to be a pain, but I have to do it.
However, these changes — as published so far — don’t appear to have a major impact on a software application like WP to Twitter.
First, a significant set of the changes regard the display of Tweets. Well, fortunately, WP to Twitter doesn’t display Tweets in any way. So, I can pretty much ignore that entire section.
Second, the next big set of changes have to do with application size. Now, WP to Twitter does have over a million downloads – which probably translates to 20 or 30,000 active users. Maybe even more. However, from the Twitter application perspective every one of those users is a separate application; so none of them are large scale applications which will greatly impact Twitter.
Third, they’re modifying the rate limiting rules. While hypothetically this could effect WP to Twitter, it’s not very likely. The limit is something like 60 calls per hour for a given endpoint. WP to Twitter uses only one endpoint – the status update endpoint – so you may run into this if you’re posting more than 60 times per hour from your WordPress blog. Possible, but not very likely.
So, on the basis of what Twitter has published so far, WP to Twitter appears to be safe. However, it is certain that these rules are not the complete set of rule changes. For now, I’ll just try and keep up with the information and find out what’s going to happen. WP to Twitter isn’t going anywhere yet.
But I do suggest that you subscribe to my blog to keep updated…
Joe Dolson; October 20, 2012 at 9:33 am
Yes, certainly you can. I don’t have a system in place yet for upgrading through my site, but you can upgrade at any time by sending me a payment for the difference and sending me your license key. (So I can be sure I’m upgrading the right account.) You can use my donation forms to send that.
Christopher di Armani; October 20, 2012 at 7:39 am
Thanks for a great little plugin, and for the news about and your attentiveness to the new twitter guidelines.
I’m just trying to decide whether the developer version price is worth it for me for the Pro version. If I buy a single site license now, can I upgrade it to a developer version license later for the difference in price?