silverpill@silverpill@mitra.social: Just for the record, I do not agree with the premises of that article.<br><br>Fediverse doesn't gradually diverge from the ActivityPub spec and software development doesn't look like you describe.<br><br>Overall, it looks like an attempt to discredit FEP process by painting it as ineffective and unsustainable, in favor of... I am not entirely sure, GitHub repo and a non-profit?

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Arnold Schrijver@aschrijver@socialhub.activitypub.rocks (2026-04-11 16:33:16)
Alt-text to the diagram. Click to expand the text.Grassroots growth has seen the fediverse gradually diverge from ActivityPub open standards.With post-facto interoperability the dominant driver, increasing protocol decay hampers innovation and growth.Fediverse as it stands today has limited its application areas, and lost attractiveness to newcomers.A shift back to open standards is possible and required for ActivityPub to remain relevant in the future.Current technology standardization process is unfit for the social dynamics in fediverse grassroots environment.Challenges to standardization are fostering shared ownership, proactive involvement, governance, and recentralization.There are four points where recentralization is a risk: server instances, app platforms, the FEP process, and W3C SocialCG.While funding is available for individual FOSS projects, it is lacking for any work on healthy technology ecosystems.Grassroots open standards allow specification documents to evolve from the bottom up in inclusive commons based ecosystems.Grassroots standardization aligns top-down protocol design with innovation in the creative cauldron of the commons.The social web offers opportunities to natively support standardization processes, and decentralize specifications.Specifications as code that may be bundled with their apps and services, and can be introspected at actor endpoints.Decentralized specification hubs can serve the interoperability needs for different interest groups and solution domains.FEP may become the fediverse evolution process and be part of protocol design that enables robust solution development.Work on the ActivityPub API offers opportunity to reposition the FEP as federated service for Grassroots standardization.With ActivityPub as a grassroots standard, fediverse can be the Future of social networking where we Reimagine social.https://social.coop/@smallcircles/116368803389082089

Thanks to @silverpill and @eprodrom, the pillars of grassroots standard
---Attachments---
https://socialhub.activitypub.rocks/uploads/default/original/2X/e/e7375986a0bf9142613042906a5dac8731f2eabd.png
https://socialhub.activitypub.rocks/uploads/default/original/2X/e/e7375986a0bf9142613042906a5dac8731f2eabd.png
https://socialhub.activitypub.rocks/uploads/default/original/2X/e/e7375986a0bf9142613042906a5dac8731f2eabd.png
---Reply---
silverpill@silverpill@mitra.social (2026-04-12 01:42:59)
Just for the record, I do not agree with the premises of that article.

Fediverse doesn't gradually diverge from the ActivityPub spec and software development doesn't look like you describe.

Overall, it looks like an attempt to discredit FEP process by painting it as ineffective and unsustainable, in favor of... I am not entirely sure, GitHub repo and a non-profit?