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.
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.