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?

perl.xyz is your onchain social arcade, powered by $DEGEN. Join the discussion at /perl

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

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

+1 to getting a key 

also to anything non trivial forced me to really pull out my wallet in a big way

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

Absolutely the dumb rate limits

Promptly sublimates from "free" to "stupidly expensive" with no nuance on usage

Auth is painful, rate limits were unclear, and the rules are weird.

I got shut down two days in because my bot tweeted something with an @ that got interpreted as a tag. Something I could do as a human nbd was an immediate ban when done as a bot.