5 ms·

Agreed, Twitter requiring you to get in touch with them should your app grow past 100k users seems like they're just setting a public limit for the point at whi

Agreed, Twitter requiring you to get in touch with them should your app grow past 100k users seems like they're just setting a public limit for the point at which they want to vet that your application is behaving correctly. From my experience with the Twitter API team, they've always been open and responsive, particularly with regards to a "Hey, I would like to do X with your API, is that alright?"-type questions. I think Twitter have taken a lot of unfair flack from this announcement, when it seems like a really positive step forwards.

MatthewPhillips 14y ago
Here's their response to the suggestion that they allow CORS: https://dev.twitter.com/discussions/1291 https://dev.twitter.com/discussions/1291 Here's App.net's: https://github.com/appdotnet/api-spec/issues/10 https://github.com/appdotnet/api-spec/issues/10 Can you spot the difference? Hint, consider the nature of the relationship between the platform and developer in each case.
- mootothemax 14y ago
  Can you spot the difference? Hint, consider the nature of the relationship between the platform and developer in each case. Be fair, you're comparing apples and oranges; a world as it would be nice to live in when discussed amongst friends, as opposed to those who have to maintain a world with just a few more people involved in it than that.
  - MatthewPhillips 14y ago
    Something tells me the support tickets with advertisers looks more like that App.net thread.
timdorr 14y ago
It seems to me that a lot of people weighing in on this situation (mainly elsewhere, not on HN) are not even developers, let alone Twitter developers. As such, they don't really have any valid contribution to the discussion and only serve to create incendiary comments and stir up controversy. From the consumer's perspective, sure, this looks like a raw deal. Twitter wants to shut down my favorite client. Those assholes! But the reality of the situation is they simply want to control the client experience so they can insert ads. Of course, this all breaks down as soon as one client lets you put in your own application keys...

MatthewPhillips 14y ago

Here's their response to the suggestion that they allow CORS: https://dev.twitter.com/discussions/1291 https://dev.twitter.com/discussions/1291 Here's App.net's: https://github.com/appdotnet/api-spec/issues/10 https://github.com/appdotnet/api-spec/issues/10 Can you spot the difference? Hint, consider the nature of the relationship between the platform and developer in each case.

mootothemax 14y ago
Can you spot the difference? Hint, consider the nature of the relationship between the platform and developer in each case. Be fair, you're comparing apples and oranges; a world as it would be nice to live in when discussed amongst friends, as opposed to those who have to maintain a world with just a few more people involved in it than that.
- MatthewPhillips 14y ago
  Something tells me the support tickets with advertisers looks more like that App.net thread.

timdorr 14y ago

It seems to me that a lot of people weighing in on this situation (mainly elsewhere, not on HN) are not even developers, let alone Twitter developers. As such, they don't really have any valid contribution to the discussion and only serve to create incendiary comments and stir up controversy. From the consumer's perspective, sure, this looks like a raw deal. Twitter wants to shut down my favorite client. Those assholes! But the reality of the situation is they simply want to control the client experience so they can insert ads. Of course, this all breaks down as soon as one client lets you put in your own application keys...