152
iOS AppStore privacy preview for Meta’s upcoming ActivityPub-based app Threads
(media.kbin.social)
this post was submitted on 04 Jul 2023
152 points (100.0% liked)
Fediverse
52 readers
1 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hopefully no credible Fediverse platform actually federates with their trojan horse. If we let Zuck, or anyone like him, become a major player in the ActivityPub world, pretty soon we're going to end up right back where we started.
Genuinely curious as I'm new to all of this, why would it matter? Isn't that the whole point of the fediverse? If their spyware app interfacing with it is what gets the casual users into it who already have Meta's spyware installed, you can still use the fediverse from whatever service you prefer, right?
Here’s a pretty thorough explanation of why this Meta app is dangerous for the Fediverse.
https://fediversereport.com/meta-plans-on-joining-the-fediverse-the-responses/
I’m still trying to wrap my head around Fediverse concepts as well but the thing that stands out for me is that there is a history of private companies effectively killing open source projects.
For us, the vulnerability is ActivityPub. If Meta begins “contributing” to a foundational Fediverse technology, they have the resources to extend the protocol in a way that benefits Meta only, at a pace that only a company with the resources of Meta can.
Yep. Just like how we don't want any particular web browser core becoming the standard core as opposed to having a common web protocols that anyone can write a browser to use. We saw what a mess people writing for only Internet Explorer became, and even Microsoft felt the pains of that when they wanted to retire Internet Explorer. The legacy of that remains to this day when coming across under or non funded web sites created through contract funding or grant funding and then not updated.
I certainly can see the same things happening long term with a large corporate entity joining the Fediverse, initially 'contributing' some great feature, and then in the future having a large number of instances dependent on that feature and having the tables turned by the corporate entity saying "Oh, well, we're charging for this now." You know... kind of like what just happened with Reddit and third part readers.