If you build a company around someone else's free API, you're either a high stakes gambler or a moron.
Or out for a quick buck without any expectation to build a lasting business.
What Happens When A Twitter Client Hits The Token Limit
11–20 of 188 posts
Re: What Happens When A Twitter Client Hits The Token Limit
#12This is really idiotic. What are they trying to do? Make sure that all the top users flock to App.net or somewhere else?
app.net is still laughable as a replacement for twitter. With the new apps it's now convenient to use a feed aggregation service that only accepts feeds from rich people, but it's still a feed aggregation service that only accepts feeds from rich people.
Re: What Happens When A Twitter Client Hits The Token Limit
#13I think some people might call this "biting the hand that feeds you". Or at least the hand that got you started.
Others might call it "getting big-timed"
Re: What Happens When A Twitter Client Hits The Token Limit
#14This is really idiotic. What are they trying to do? Make sure that all the top users flock to App.net or somewhere else?
No, they're making sure users flock to twitter.com instead. And it's been effective, since I use the web interface instead of Tweetbot now!
Re: What Happens When A Twitter Client Hits The Token Limit
#15*The effective rule, therefore, is even simpler: “Don’t build anything for Twitter.” Exactly, that's precisely the message they wanted you to have. What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do. I don't get anyone is surprised, it's Twitter's ecosystem and if you're duplicating their functionality then it's pe…
> What's wrong with using the twitter.com on Windows8, do we really need a special client just for Windows 8? This is exactly what the web is supposed to do.
Native > Web, if you do it right. Web has a lot of UX limitations native apps don't have.
Re: What Happens When A Twitter Client Hits The Token Limit
#16You know, back before APIs were all the rage, people wrote clients for web services by scraping. Twitter really wouldn't be able to do anything about a Twitter client that pretended to be IE9.
I've had a bot blocked by Myspace when I resorted to that. They started redirecting all my requests to " http://google.com ". And I was just working on an old Thinkpad running Ubuntu server in my dorm room, so I have to think blocking me was an automated response.
I'm sure Twitter knows how to block crawlers, especially ones that they're actually aware of.
Re: What Happens When A Twitter Client Hits The Token Limit
#17It is surprising that their response does not include a call to action with respect to their business development team. Why isn't there a 'click here to sign up to by a 10,000,000 token' link in that email? Now granted the result might be the same, people not developing for their API but at least they could get value pricing information as part of the transaction.
Re: What Happens When A Twitter Client Hits The Token Limit
#18It's so sad to watch such a lively lovely service remove the fun by destroying the values that made it great.
Meanwhile we are sitting here saying "charge us money, you fools", and they are deaf to us.
Twitter: your online site is usability hell, your own clients are dated and painful. Above all we have one question: why? Why are you intent on this path of foolishness based on placing customers and developers last?
Re: What Happens When A Twitter Client Hits The Token Limit
#19You know, back before APIs were all the rage, people wrote clients for web services by scraping. Twitter really wouldn't be able to do anything about a Twitter client that pretended to be IE9.
To what end? You're going to base a business on scraping twitter.com? That sounds like a much worse idea than trying to work within the API.
Re: What Happens When A Twitter Client Hits The Token Limit
#20If my salary depended on the Twitter API right now I'd be scared shitless.
Unless you work for Twitter, I'd say you're right, and rightly so. Don't depend on someone else's API, how many times must history repeat itself before this message sinks in.
That's a ridiculous statement. Unless you are as vertically integrated as Apple, you can't avoid dependencies on someone else's APIs.