News for hackers. Stuff that matters.
Re:“It appears that Twitter is DDoSing itself” by amelius on Saturday July 01, 2023 @04:32PM (#36554847)
I'm sure the loads are not comparable.
Re:“It appears that Twitter is DDoSing itself” by brucethemoose2 on Saturday July 01, 2023 @04:40PM (#36554950)
Doesn't really matter if it works?

And if some massive org needs bandwidth for posts, can't they host their own public instance? I'm sure many organizations would prefer that over being at Twitter's mercy.

Re:“It appears that Twitter is DDoSing itself” by paradaux on Saturday July 01, 2023 @04:37PM (#36554920)
Equally, neither is the budget. Load isn't an excuse.
Re:“It appears that Twitter is DDoSing itself” by hinata08 on Saturday July 01, 2023 @04:39PM (#36554937)
It withstands being one of the first link on HN, and it still loads comfortably.

For a personal website, that's a great performance.

Re:“It appears that Twitter is DDoSing itself” by WJW on Saturday July 01, 2023 @05:00PM (#36555149)
HN traffic is not nearly the DDOS people make it out to be. I made it to spot #2 once and that was a few dozen hits per second at most. Maybe not something to serve with wordpress from a raspberry pi, but hardly apocalyptic levels of traffic.
Re:“It appears that Twitter is DDoSing itself” by hparadiz on Saturday July 01, 2023 @05:02PM (#36555178)
Wordpress on a raspberry pi will handle static, properly cached content just fine.
Re:“It appears that Twitter is DDoSing itself” by distantsounds on Saturday July 01, 2023 @05:50PM (#36555661)
previous HN articles linking to instances has caused them to become overloaded. this instance just seems to know how to handle it
Re:“It appears that Twitter is DDoSing itself” by vGPU on Saturday July 01, 2023 @05:59PM (#36555730)
HN itself is run on a single server. So long as you’re not running something bloated or trying to host on a DSL connection, you’ll be fine.
Re:“It appears that Twitter is DDoSing itself” by candiddevmike on Saturday July 01, 2023 @04:54PM (#36555082)
It's not crunching a bunch of analysis or ads in the background. I bet it scales wonderfully with maybe some kind of cache/CDN if necessary.
Re:“It appears that Twitter is DDoSing itself” by dijit on Saturday July 01, 2023 @05:51PM (#36555667)
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 a shit about user experience.

This also goes for when “complicated” systems fail, maybe making them so complicated and centralised is not the way.

Re:“It appears that Twitter is DDoSing itself” by kevin_thibedeau on Saturday July 01, 2023 @06:04PM (#36555773)
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.
Re:“It appears that Twitter is DDoSing itself” by tedunangst on Saturday July 01, 2023 @06:42PM (#36556096)
How do plan to send me an email without talking to my mail server?
Re:“It appears that Twitter is DDoSing itself” by kstrauser on Saturday July 01, 2023 @06:28PM (#36555996)
I genuinely don't understand what you mean here. I don't directly access any peer's server when I want to talk to them.
Re:“It appears that Twitter is DDoSing itself” by jtode on Saturday July 01, 2023 @05:58PM (#36555721)
I've been arguing with Twitter emigres who seem to think that the UX on masto sucks.

I would say that Twitter is an automatic transmission, mastodon is a standard.

Re:“It appears that Twitter is DDoSing itself” by latency-guy2 on Saturday July 01, 2023 @07:52PM (#36556582)
I couldn't see a few threads on Mastadon a few weeks ago, the post was up for 24 hours, and the perceived outage never dropped through that entire period, and probably longer after I stopped caring about the post. There were numerous people on HN experiencing the same.