4 ms·

This reminds me of Soundcloud a few years ago when they were giving away API access for free for unlimited plays but then were almost close to bankrupt and pret

This reminds me of Soundcloud a few years ago when they were giving away API access for free for unlimited plays but then were almost close to bankrupt and pretty much shut down all API plays. I ended up shutting down my 3rd party app then but not sure what's their API limits now. Twitter recently made huge changes to their API limits too which impacted a lot of 3rd party apps. I hope Unsplash doesn't end up similar to those.

HelloFellowDevs 8y ago
On the note of Twitter's restriction of API usage, Jack talked about it recently on the podcast Tales from the Crypt [0]. He doesn't give any specifics but attributes Twitters early struggle with uptime to unrestricted API usage [1]. [0] https://podcasts.apple.com/us/podcast/tales-from-the-crypt/id1292381204 https://podcasts.apple.com/us/podcast/tales-from-the-crypt/i... [1] https://overcast.fm/+KiHpBJHGo/15:30 https://overcast.fm/+KiHpBJHGo/15:30
- ma2rten 8y ago
  That seems silly to me. They could have easily served their api from another server.
  - barrkel 8y ago
    I imagine the problem wasn't API servers but data access.
    - ma2rten 8y ago
      I meant both api servers and database replica.
- ceejayoz 8y ago
  > He doesn't give any specifics but attributes Twitters early struggle with uptime to unrestricted API usage. Of course, that was also critical to Twitter's success.
- Nextgrid 8y ago
  Jack has proven himself a liar many times with his false promises regarding taking care of the abuse problem on his platform without success so I’d take anything he says with a pinch of salt. Let’s also not forget that they have a vendetta against third-party clients (so they can push their own client with the bullshit algorithmic timeline and ads) so it wouldn’t surprise me that he says that just as an excuse. In reality their web access was just as unrestricted as their API so it should share some of the blame too.

HelloFellowDevs 8y ago

On the note of Twitter's restriction of API usage, Jack talked about it recently on the podcast Tales from the Crypt [0]. He doesn't give any specifics but attributes Twitters early struggle with uptime to unrestricted API usage [1]. [0] https://podcasts.apple.com/us/podcast/tales-from-the-crypt/id1292381204 https://podcasts.apple.com/us/podcast/tales-from-the-crypt/i... [1] https://overcast.fm/+KiHpBJHGo/15:30 https://overcast.fm/+KiHpBJHGo/15:30

ma2rten 8y ago
That seems silly to me. They could have easily served their api from another server.
- barrkel 8y ago
  I imagine the problem wasn't API servers but data access.
  - ma2rten 8y ago
    I meant both api servers and database replica.
ceejayoz 8y ago
> He doesn't give any specifics but attributes Twitters early struggle with uptime to unrestricted API usage. Of course, that was also critical to Twitter's success.
Nextgrid 8y ago
Jack has proven himself a liar many times with his false promises regarding taking care of the abuse problem on his platform without success so I’d take anything he says with a pinch of salt. Let’s also not forget that they have a vendetta against third-party clients (so they can push their own client with the bullshit algorithmic timeline and ads) so it wouldn’t surprise me that he says that just as an excuse. In reality their web access was just as unrestricted as their API so it should share some of the blame too.