The sad truth about #TwitterLimits is coming up. ‼️💥
#Fireship as always, in an ironic, brilliant and informative way, reveals what I previously brought (see below). The #RateLimitedExceeded issue is not exactly related to fighting #bots at #Twitter.
There are some more clean and effective solutions to do so. Being limited by GCP available resources or forcing users to subscribe to Twitter Blue is a more logical explanation.
youtu.be/3AS5x05XIyg
#ratelimit #bitcoin nostr:note19g3nvaum6vps76ddgzpjytc7a5zjf5akkh76zhrdghjwezpuq4vqa2fsy9
Agree. I am angry with this move. Totally unjustified.
For me today it was fine. Just in the morning it was blocked
How are you accessing it? Currently with the iPhone app is totally unusable. With the Android I see no problems.
I did not try via web browsers.
Very disappointing status at the moment. In a previous post I explained why the bot issue is bs.
I don’t buy the #twitter daily #ratelimit as a measure to fight bots.
It’s like using a bazooka to kill mosquitos.
I believe the real reason is to increase blue Twitter subscribers.
To block unauthenticated HTTP requests, you can use a bot defender that challenges connections if the rate exceeds some threshold. For example with captcha. If challenge fails the IP can be blocked temporarily
To limit authenticated users, minute rate limit is the best solution (Daily is absurd!) However I don’t even get why to block the Twitter app users (easily identifiable). The UI is already preventing massive posts display.
nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9 nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m anything wrong in my assumptions? Always ready to learn.
Thanks a lot for your advice and sorry to have brought an unoriginal point!
I ll try to upgrade! 🤣
Trying to understand how to look for people here 😅😂
#introductions
Nick, having fun learning Cybersecurity, AI, and playing with Big Data systems in the Cloud.
Happy to be here
#refugeefromTwitter