@paul it looks like the rate limiting (maybe just a regex against the request?) is being done on stuff in the [x]/api/ namespace, which prevents the home timeline from loading. hits to /notifications still work.
super crude 10 minute 'fix' to prevent anything from scraping /home, i guess
@paul I'm also expecting him to start limiting number of tweets per IP or number of accounts used from one IP so that you can't get around the limit with multiple accounts…
@paul I would say don't give them any ideas but at this point, nothing would surprise me about that company. Bring back Fleets just for the hell of it. Couldn’t hurt, nobody could load it anyway.
@paul For a minute, I thought he was referring to the API. This guy is insane. Truly insane. Even Meta could not come with such a stupid idea of limiting your users so hard.
@paul I’ve been at a rate limit since around 10am. If that means I’m unable to use his service for the rest of the day, seems pretty dumb in his part. I guess I’ll look tomorrow maybe?
@paul Wonder if they have anyone left there willing to point out to him that the companies & creators posting tweets are gonna be bothered by the idea that not as many people will see their tweets?
@paul I got shadow banned on Titter by the head boob Elno Muck. Maybe he can do us all a favor and go to Mars first. 🚀 👨🚀 He should bring his boring machine to drill a hole big enough for his head to fit in. 🪐🕳️
@paul lol. I opened the app this morning, browsed through some posts, accidentally tapped the “For you” page (which I would never do intentionally) and I’m rate limited for the day. What a travesty of an app Twitter has become. We’ll done, Elon.
Add comment