110
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2023
110 points (100.0% liked)
/kbin meta
2 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 2 years ago
A lot of the FUD regarding #Threads joining the #Fediverse has been put to sleep by #Mastodon on this blog post:
https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
"The fact that large platforms are adopting ActivityPub is not only validation of the movement towards decentralized social media, but a path forward for people locked into these platforms to switch to better providers."
Also @daringfireball made this blog post that I agree with:
https://daringfireball.net/linked/2023/06/19/not-that-kind-of-open
"the idea that administrators of Mastodon/Fediverse instances should pledge to preemptively block Facebook’s imminent Twitter-like ActivityPub service (purportedly named Threads) strikes me as petty and deliberately insular. I don’t like Facebook, the company, and I’ve never seen the appeal of Facebook, the product (a.k.a. “the blue app”). But there are literally billions of good people who use their services. Why cut them off from the open ActivityPub social world?"
There are a lot of good reasons to not let corporate media join the fediverse: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
I understand, and I do remember the XMPP debacle, but I also remember that back then people trusted Google and their do-no-harm motto, and they really wanted them to lead in the real-time voice/video chat arena, and in order to make it Google made some protocol desitions that broke away from XMPP.
This time around we don’t trust Big Tech and will not try to adjust to their ways, if they want to they can embrace ActivityPub or not. The rest of the Fediverse will not try to apply their tactics or monetization to the protocol. Either they adhere to the stardard, or their users will have no compatibilty with the rest of the Fediverse.
I am not suggesting we all embrace them and try to make them feel welcome, but let's not close our instances alltogether to them, let each person decide for themself if they want to follow people from their instance or not.
Servers decide instances they federate with, not users.
Users decide servers based partly on what the server federates with.
Leaving the what servers to view/block decision up to every user is a very cumbersome solution to a problem that is already elegantly solved.