Liz
Liz
Huh... I'm not sure *how much* I like this fix, especially since production QTweet hasn't ever been stuck on a destroy loop... But I have seen users report issues with...
As you said this is a case of docker-compose not being installed on your machine. Yeah the thing is I got on Docker so people on Windows, Mac and Linux...
I like this idea! I could implement it without breaking the current database scheme, too :)
After looking into this, the twitter api doesn't provide a way to differentiate between threads and replies :I
Alternatively, I could provide a `--noreply` option for users who simply do not wany any replies.
Thoughts: I feel like a vast majority of subscriptions on qtweet are for content, media, that kind of stuff, where it doesn't really matter if it's posted with a delay....
Another solution... Than twitter?
> No no! Solution for the 5k limit. There are no other solutions except for the Enterprise API. The Enterprise API is far, far from our budget, Twitter won't even...
> Do forgive me if this is a dumb suggestion (it probably is), but would it be possible to cycle through subscriptions to work around this limitation. What I mean...
@trodiz Yes but I'm limited to 900 calls to that endpoint per 15min window. With 5k users that is simply not manageable :(