You must log in or register to comment.
wow, this is actually amazing.
You’d think a rapidly developing service like Lemmy might face restrictions like that due to resources but Twitter? Mismanagement beyond belief.
Please please please let this be the breaking point at which big online personalities switch to mastodon, or at least start using those crossposting tools. That’s the only thing I miss from twitter and something RSS cant replace
I’m shocked, SHOCKED that killing the API would lead to web scraping! That was a completely unpredictable outcome.
By post he means tweet, right? Google says average tweet length is only around 30 characters and average word length around 5 characters. So let’s say it’s 8 words with abbreviation which would take 2 seconds to read. If it’s 4 seconds per tweet with scrolling then you can now only spend under an hour on Twitter without paying. Good on him for fighting against social media addiction I guess.
Dude is using 100% of his brain to find the best way to cut ad revenue.
I got rate limited in 25 minutes by refreshing my Following feed and reading about people getting rate limited. I don’t think it counts 600 unique tweets since I definitely reloaded the same tweets multiple times.
Well, Twitter is a mobile game now… Is there something to consider it a gacha?
spez right now:
I for one am cheering its demise.
You really can’t make this stuff up, it’s beyond my head how someone can make those choices. But I mean advertisers already ditched Twitter long ago, so why not squeeze the last money out of it that you can get.
The funny thing is I’m pretty sure replies, tweets, and retweets all count toward that (if they’re using the same rules as the API), so basically that just kills the majority of your user base.
Why would you punish your users for using your fucking site? It’s kinda sad how Elon is ruining Twitter.
He is so unbelievably dumb?? 😅
Limit READIND is something new. What a creative move!
I wonder what’s actually going on; I doubt it’s about “scraping” and “manipulation”
For my money I would bet the issue stems from abandoning Google server hosting, either from arrogance or being unable to afford it.
Oh yeah I completely forgot about that particular idiocy, Elmo gets up to so much stupid shit that it’s hard to keep track.
But I’d also be willing to bet money on this being somehow at least partially tied to ditching GC, likely due to not being able to pay (at that’s what is implied by them refusing to pay the bill.) I guess Elmo thought “how hard can running some servers be? I’m a rokit skientist” and decided to just skip paying the bill as a power move instead of trying to make a deal with Google, and now the remaining developers, ops people etc. – those poor bastards – are paying the price.
That’s my bet too. They weren’t hosting the site itself on GCP but they were using them for trust and safety services, and I bet that one of those services was anti scraping prevention with things like ip blocking and captchas, which would explain why scraping suddenly became a problem for them the day their contract ended. It can’t be a coincidence.
This is second-hand, so take it with a grain of salt, but I’ve seen mention of a bug that sometimes causes the same graphql query to be executed in an infinite loop (presumably they’re async requests, so the browser wouldn’t lock and the user wouldn’t even notice).
So they may essentially be getting DDOS’d by their own users due to a bug on their end.
Edit: better info: https://sfba.social/@sysop408/110639435788921057
Ha, that’s hilarious. Absolutely not a surprise, though
Simply put this is the most amazing thing the twit did to Twitter since forcing himself as King Twit. Even better than when he tried to back out of it but couldn’t because he’d already signed for it.
