What do you think are the chances this is related to them having trouble paying their cloud services bills? That's the first thing that came to mind when I saw that was happening, the reports of how the cloud services contracts were among the ones Elon decided to stop paying once revenue shrunk.
If that was just this week, it might not be a coincidence. Maybe they had to negotiate something out for less bandwidth then they were getting before.
@mmasnick @Biohazardous Musk is notoriously cheap, and Twitter is broke, so likely it paid for some lowest tier for the new quarter. And then they broke the clients with their self-inflicted DDoS and blew through their entire low-budget third-quarter data cap within a day or so.
Attached: 1 image Lest anyone doubt that Twitter was idiotic enough to release code that would cause a race condition and result in its own users executing a DDOS attack on it, here's the network console readout from Firefox showing all the network requests blasting away. Of course I immediately closed out my connection because I'm a good person. Oh, but it's the weekend and Evil Sheldon is in control so I kept the party going for a while since Twitter insisted on it. #TwitterDown #Twitter #MastodonMigration #DDOS #TwitterFail #SelfDDOS
@Biohazardous @mmasnick a few days ago there was talk of Twitter denying anonymous access, which was promptly skated around by people using web scrapers on throwaway accounts
This has the smell of a poorly thought out reaction to that
Irrelevant platform becomes more irrelevant. Nobody likes Twitter anymore. Remember when it was useful and stuff?
@mmasnick this would be insanely dumb even with astronomical limits set just to kill scrapers.
But 600/day for regular users? On a platform you're trying to sell ad impressions on?
I hit the limit in 11 minutes casually scrolling. You can't even read your own tweets and their replies without gas-pedaling into your rate limit with it so low.
A single viral or controversial tweet and you're done.
@mmasnick APIs were created as a more efficient way of getting to data versus web scraping. So when he killed API access, of course devs turned back to web scraping to get the data.
No doubt that created additional load on the servers, so he thinks limiting access to the data via requiring an account to view tweets and rate limiting web resources is a good solution.
But now he's just limited ad exposure. Aren't ads a large driver to revenue? So, yeah, this is tremendously stupid.
@atoponce @mmasnick
I know right. All that whining about the expense of running the API, both from Twitter and Reddit, and I'm sitting there thinking: I'm old enough to remember when engineers built these things for exactly the reasons you describe.
It's like all the actual engineers have left these companies and the techbros running them now are people who've never benchmarked a service in their lives.
@caneroncu @mmasnick It's all about web scraping. Tweets are no longer public. They're behind a login, which means all embedded tweets in blog posts and such broke. This effectively cuts off scraping tools. Which means only logged in accounts can web scrape.
Soooo, he's rate limiting logged in accounts to also limit web scraping. The 6,000 vs 600 & 300 limits is just a perk to subscribe to Twitter Blue.
Further, requiring logged in accounts also means you can track who is scraping.
Don't worry. He's thought of that.
Viewing an ad doesn't count towards your limited quota
https://tenor.com/en-GB/view/smart-gif-20689814
They have talked about... ~12 times so.. ♟️💥💨
Well, when you don’t pay Google cloud services…
@mmasnick hmmm, interesting. Thanks for correcting this.
There's got to be something more about the significance of today. Whatever the real reason, it's obvious he's unable to manage.