Colin
@colin
For those of you that have used the Twitter API, what are the biggest challenges you’ve faced? Rate limits, uncertainty about endpoints being shutoff, cost, etc?
7 replies
0 recast
0 reaction
Peter Kim
@peter
rate limits that make it impossible at times to build an app that could actually scale to a significant number of users the streaming api v2 is pretty good though. That's what we're using for @perl on twitter for auth use this library: https://github.com/PLhery/node-twitter-api-v2
0 reply
0 recast
0 reaction
Brian
@brianj
+1 to getting a key also to anything non trivial forced me to really pull out my wallet in a big way
0 reply
0 recast
0 reaction
Greg
@greg
rate limits
0 reply
0 recast
0 reaction
Matt Rickard
@mattrickard
v2 is an improvement but still misses the mark - Not enough clients (had to put one together myself for Go) - Filter endpoints don't make much sense - Query language for filters is terrible
0 reply
0 recast
0 reaction
Lucas Baker
@alpha
Absolutely the dumb rate limits Promptly sublimates from "free" to "stupidly expensive" with no nuance on usage
0 reply
0 recast
0 reaction
pugson
@pugson
getting a key lol
0 reply
0 recast
0 reaction
