Beady Belle Fanchannel@Profpatsch@mastodon.xyz: I'm thinking of replying in a blog post as someone who has spent the last three months actively developing a fediverse application (#flohmarkt).<br><br>But the most critical thought: I miss a discussion about reducing implementation complexity as much as possible. The standards leave much "wiggle room" for implementation, which I think is partly to blame for the "whack a mole" nature of support

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

Note Detail

Beady Belle Fanchannel@Profpatsch@mastodon.xyz (2026-04-10 14:11:30)
Arnold Schrijver (@smallcircles) just published a fairly long thinkpiece on the future of ActivityPub and the fediverse and how we could achieve a grassroots improvement of the standards. It's well worth a read! 

https://coding.social/blog/grassroots-evolution/#fediverse-tomorrow

#activitypub #fediverse #FEPs #fep #fedidev
---Reply---
Beady Belle Fanchannel@Profpatsch@mastodon.xyz (2026-04-10 14:14:43)
I'm thinking of replying in a blog post as someone who has spent the last three months actively developing a fediverse application (#flohmarkt).

But the most critical thought: I miss a discussion about reducing implementation complexity as much as possible. The standards leave much "wiggle room" for implementation, which I think is partly to blame for the "whack a mole" nature of support


---Replies---

Beady Belle Fanchannel@Profpatsch@mastodon.xyz (2026-04-10 14:21:24)
Things that come to mind:

* Inbox signature validation is very vague
* jsonld is a complex standard that introduces a need for libraries, leads to slowdowns and blows up the implementation surface
* Interaction schemes like quoting requests lead to nontrivial state machines

In general: any MAY in a definition explodes the possible things that can go badly.
Which is why I think we need to use a different approach from how e.g. RFCs are structured