Earlier quoted context omitted.
A union vote is the only way to save that platform. Either unionize or let the company die.
[flagged]
Twitter Is DDOSing Itself
321–330 of 1001 posts
Re: Twitter Is DDOSing Itself
#322Earlier quoted context omitted.
> On Mastodon simply discussing certain topics will get you banned, and instances that don't ban those users get defederated. This is why P2P is superior. Federation nodes can be used to strong-arm collective behavior against the will of individual users. I don't mind being exposed to liberal and conservative thought. I want to consume almost the entire spectrum of human discourse so that I can synthesize ideas for m…
Then just make your own instance? Or is the complaint that you don’t have the power to force yourself on people who don’t want to read your shit?
Re: Twitter Is DDOSing Itself
#323Oh come on. This is console.log spam. This isn’t a “self-DDoS”.
Re: Twitter Is DDOSing Itself
#324Re: Twitter Is DDOSing Itself
#325Earlier quoted context omitted.
A union vote is the only way to save that platform. Either unionize or let the company die.
[flagged]
Unions are the reason we have a minimum wage, limited work week, paid holidays, equal pay for equal work, unemployment benefits, workers' comp, the family medical leave act, and many more things. If not for unions we would all still be doing sixty hour weeks getting paid in company scrip.
"Socialism" brought us Social Security, Medicare, child labor laws and agriculture subsidies, health insurance, food assistance, housing subsidies, energy and utilities subsidies, and education and childcare assistance. And it brings the rest of the modern world free education and healthcare.
Re: Twitter Is DDOSing Itself
#326My 14yr old daughter sent me this screenshot the other day with the comment "I think that one sentence sums up twitter pretty well". https://capture.dropbox.com/GqgTAxRimqAXzrdo
Re: Twitter Is DDOSing Itself
#327This bug is very unlikely to be the reason. The rate limiter on the server side is cheap and the frontend bug only gets triggered with the rate limit active. I have seen similar bugs in the systems I oversee because network libraries love to retry requests without sane limitations by default. But I never saw them make our rate limiters sweat. It's slightly more annoying when they hit an API which actually does some e…
One thing about having leadership that is known to lie about anything or everything, for any sort of imagined personal gain, is that the very concept of truth is destroyed. I agree that this is probably not the bug at the root of it all. But I also don't believe the story that Musk is selling for why he's in effect shutting down the site. But both could be true and I'm still thinking about other potential reasons, a…
I will note that the few times I investigated claims of Elon lies they were not proper lies, either being misunderstood, misleading (which IS unethical, don't get me wrong), of indeterminate truth value (he said, she said type stuff), delusional optimism or actually true.
Like journalists, Musk rarely outright knowingly makes literally false statements, but this does not mean you should take what he says at face value.
Re: Twitter Is DDOSing Itself
#328Anybody knows if these requests were happening before the login only change? Because it would be hilarious if huge scrapping operation was a bug in their javascript.
I can say for sure that a certain flow ("back" from Profile view or similar) would trigger an infinite redirecting loop on Firefox on my Android device, with probably dozens of requests over a couple of seconds until rate limiting kicked in. Maybe there were many of these little bugs which together looked like some kind of DDOS or scraping.
Re: Twitter Is DDOSing Itself
#329So, there may be a much simpler explanation for why their new rate limits on regular users to can-barely-scroll levels, and how that has all sorts of unintended consequences they weren't ready for
Re: Twitter Is DDOSing Itself
#330Earlier quoted context omitted.
Honestly. what the fuck is this response? I hear always that centralising everything is great because efficiencies of scale: but then we have something that works as good or better and the response is; “ah yeah, but the load is so high!” Why do I care? I don't honestly give a shit about how much load you have, you could be factoring Pi on every page load; it means -nothing- to me. I kindly invite you to give more of…
Mastodon isn't truly decentralized. Every instance is its own feifdom and you have to communicate directly with them to exchange messages. This is unlike how Usenet, FidoNet, and SMTP work. They are truly decentralized as you can exchange data without directly accessing a peer's host server.