3 ms·
They're taking it slow at least in part because there were concerns about threads traffic overwhelming mastodon servers.
by empath75 2y ago
They're taking it slow at least in part because there were concerns about threads traffic overwhelming mastodon servers.
- krapp 2y agoThat shouldn't be a huge problem - many Mastodon servers are already blocking Threads by default.
- dewey 2y agoMost people are probably on the 3 biggest instances and the "official" instances don't have it blocked as far as I can see (https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/ https://blog.joinmastodon.org/2023/07/what-to-know-about-thr...). Blocking also seems like a silly thing for a network that is about being open and interoperable.
- mkarliner 2y agoQuite, and, as I said in my post, I think we (the Fediverse) owe it to the rest of the Internet to enable the deconstruction of the current social media landscape as much as possible.
- krapp 2y agoThe protocol is open and interoperable. I can't build a Facebook but nothing is stopping Mark Zuckerberg from building a platform on ActivityHub. But there would be no point to a federated network if every node were required to accept traffic from all other nodes. That's just centralization with extra steps.. and centralized social media is what most people who move to federated networks are trying to avoid, to say nothing of the cost burden on smaller instances to handle all of that traffic. A lot of people block the big instances as well for similar reasons.
- immibis 2y agoIs blocking spam a silly thing?
- dewey 2y agoNo, but "spam" is subjective and while you can decide that for your own instance, doing it for a bigger instance on behave of your users seems a bit overreaching...but luckily I can just move to an instance where I agree with the rules or host my own.
- immibis 2y agoIs blocking spam a silly thing? (Google Groups was to Usenet what Threads is to ActivityPub, and it got collectively blocked by all Usenet servers for spam, then decided to shut down.)