211–220 of 1001 posts
It's not a self ddos if twitter isn't going down. You can see in the video twitter is properly handling the load and is returning HTTP 429 when the client is sending too many requests. Hitting the rate limiter or requesting a post is light weight. It's not like it's spamming login requests which require a lot of resources due to key stretching.
2 Nines is sufficient at scale?
Earlier quoted context omitted.
Well, it's a FOSS self-hostable server program. Mastodon isn't a service, so it's not susceptible to enshittification per se. A particular Mastodon host, sure. But Mastodon itself is just a codebase.
Make no mistake though, enshittification follows the population. Mastodon is about as protected as html in that sense. Could you build a nice lean mean performant static site in html? Of course, but hardly anyone does that. Most popular sites that you are able to discover these days are enshittified because the incentives favor that.
I think you're probably using the term "enshittify" differently than the parent comment. Enshittification, at least as I tend to see it used, doesn't really follow from a particular technology stack, but more about how an organization itself approaches its end users, particularly against over-exploitation/monetization of a given platform. It typically doesn't speak to the underlying technology (i.e. html vs. MB of Javascript vs. WASM), since that is (within reason) somewhat orthogonal to how the organizations running instances treat their users/how end users actually experience the platform.
Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…
In the case of Twitter, the new owner has thoroughly broken the advertising business and is trying to aggressively pursue a new version of the data business Twitter once had-- E.g. Google's Caffeine, which Twitter also eventually lost https://searchengineland.com/google-search-algorithm-change-... ... The statements about "too many scrapers" are almost certainly as illegitimate as the previous pre-acquisition statements about "too many bots."
The nature of business is that there's no judiciary or referee... the purpose of a business is to make money. Tech businesses just happen to hire lots of academically-oriented engineers who developed their skills in a different environment. It's possible to build a culture of "fairness" in a business, but at the end of the day even Google dropped "don't be evil."
One weekend Russia attacks Russia, next weekend Twitter attacks Twitter.
I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now. It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.
I dunno. We are several months out after the major layoffs. Maybe some very recent bad decisions were made internally that pared back too far, but I think Musk has long since been proven correct that the core platform could function on a fraction of the workforce it had at the time of takeover.
Engineering isn't like service positions where the lack of competent personnel is felt immediately; the debt keeps growing until your whole system collapses under it one day, how far the day is in the future depends on what system you're working on.
I think we're about at the point where the people who predicted chaos at twitter after Elon basically fired most of the experienced engineers have been proven correct. The duct tape is all coming apart at the seams now. It isn't quite as decisive as a submarine imploding, and ceasing to exist, but it has turned into a brightly burning tirefire.
25 years of products being honed for shareholder value, instead of customer or user value. We may be at peak consumer tolerance for anti-pattern, in-app purchase, subscription-model, ad-packed, data-siphoning, dopamine driven, gated experiences.
It's not a self ddos if twitter isn't going down. You can see in the video twitter is properly handling the load and is returning HTTP 429 when the client is sending too many requests. Hitting the rate limiter or requesting a post is light weight. It's not like it's spamming login requests which require a lot of resources due to key stretching.
So the result wasn't an outage, it was a radical reduction in functionality.
I think that still qualifies as a self-ddos.
Earlier quoted context omitted.
When someone says, "certain topics will get you banned" that doesn't make me judge the platform, that makes me judge the person. People are going to assume it's something you don't want to name, if you won't name it.
I'm LGBT and my spouse is trans. I don't believe you should silence anti-trans rhetoric. I believe you should engage it. The ability for /r/conservative to ban my counter arguments is just as harmful as Mastodon shutting down the anti-trans positions. Conversation is what moves us forward and is how we find commonality. I grew up religious and conservative. I changed a lot of my viewpoints through friendly conversati…
And you're free to engage the people who want to put you and your spouse on a train car in conversation all you like. Maybe you'll deprogram one or two, but you'll just help spread their propaganda to exponentially more people than you could ever help.
I have no commonality with such people and don't want to find any. I don't want to share a society with them, and I know they don't want to share one with me. I certainly don't want to debate the Jewish Question or "groomers" or race science with them on my gamedev instance.
>We're all suffering though this world together. Laugh away our differences and find the ways and the things that we share.
You know these people want you dead, right? They don't believe you have a right to exist. You and your spouse. Especially your spouse. We're not talking about a difference in belief about tax laws or support for opposing soccer teams here. "Laugh away our differences?" I'm sorry but with all due respect fuck that.
One weekend Russia attacks Russia, next weekend Twitter attacks Twitter.
Don't forget when Reddit attacked Reddit two weeks ago.
I really dont understand how the "investors" who will end up holding the bag after the IPO dont see that.
wow. how would one even fix this without deliberate downtime? you'd have to deploy and hope that the frontend will make it through CDNs to reduce pressure, right?
Barring that, turning off server side throttling or atleast making it less aggressive to slow the retry storm seems the most reasonable.