A warning to hackers: be careful building on Twitter's API

I'm still subject to some rules, but a heck of a lot less than the gardens you guys develop in like Facebook, Twitter and AOL.

I included AOL, because while it seems ridiculous someone would do that today, people used to until they got horrifically burned, and I think it'll be the same with non-decentralized platforms like FB and Twitter in the future.

Once again, my platform is the Internet.

The natural thing to do is to make it a paid solution. You inform your users of the situation and say that in order to keep the service up and running you will start charging a signup fee of $1, the same as you would pay for a mobile app. Existing users however, get 50% off and only pays $.50. Give them a month to paypal it in and then another month of repeated notices to inactive users. After two months there will probably 50k+ users you will have to close out from the service. But give them an option to restore it easily.

This is not at all unreasonable, no one would ever be able to say so. Above all it would be a tremendous learning experience for you. Perhaps you also will make a few thousand dollars in the process, but that would not be the point.

There are two alternatives to this as I see it. Either you do the above but the only thing you require is for users to manually report in by clicking a button in a form. You will still be able to weed out thousands of accounts.

The other is to set up Smart Tweets 2, hosted on another ip, and refer new users there. Explain why and make it into something funny for the users.

Whatever you do, do something bold enough to make it to Techcrunch a second time.

Facebook, twitter, linkedin, google. All of them are in the data business and sell that data to make a profit. They don't really care about the devs as they just see the devs as a way to bring people to their ecosystem; the more small apps people write, the more ways they might be able to get data. But, if they get big enough, and all of them have, they can cut you out.

I understand building a business around someone else's data (cottage industry), and I would never say not to do it, but it isn't without peril. Though, I would do it in a heartbeat for a lifestyle business that I knew I could pivot on or build another if it failed.

There are several ways to get around this. Be a middleman that publishes to both Facebook and Twitter (a reverse FriendFeed). Or, sell a software product for the user to use to move his own tweets to Facebook. A user obviously owns his own content and can put it wherever he wants. A third party app, perhaps not.

(Also, why not just get tweets via whatever method the native UI gets tweets from? Do it from AWS if you are concerned about an IP ban.)

Since most of you probably don't know me, I'm director of the platform at Twitter.

Let me know any questions/comments you might have. I'm interested in an open discussion about it.

Ryan / @rsarver

And who can blame them, providing 100,000 user tweets isn't free. Not sure where he got the idea he would never have to start paying.

Turning off basic auth also hastened this demise - whereas you could once pull whatever data you wanted from Twitter using a simple curl command, now you have to figure out OAuth. It's not that much of a challenge, but it is enough of a barrier to entry to dissuade somebody who's got a couple hours on the weekend and wants to have some fun.

Finally, their partnership with Gnip is yet another indicator that this is simply not the days of the wild west anymore. You want the data, you'll have to pay.

I recommend that you alter your product to conform to their rules, even if it makes your product a bit worse.

The scheme could be opened to provide unofficial paid APIs for Twitter and other 'walled gardens' that make data available to unauthenticated users on the Internet.

Building your business around web apis without an SLA is the most risky business, you don't have control,

Enjoy your 15 minutes of your application placebo fame!

And honestly, that style guide is ridiculous. Way to alienate your earliest champions, Twitter.

So when Twitter started hanging (and eventually timing out after a minute or so) the app basically ate one of their shared servers and the host took my whole account down for 24 hours.

I could be way off the mark, but that's how it appears to me. Multiple apps with the same purpose that require lots of resources... makes sense to stick with one or two high users and limit the rest.

The reason sounds fishy, and his retort is well-founded, but it's an important thing to note.