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.
-
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
-
System shared this topic on
-
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
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
-
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
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 machinesIn 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 -
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 machinesIn 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 structuredHey, thank you! Delighted you found my article even before I announced it on fedi
https://social.coop/@smallcircles/116379158584600016
Thus far my poll on readership found 4 Meh skips. AI vs. long handcrafted thinkpieces: 1 - 0?
We'll see. Finding that out is also SX, after all.
-
Hey, thank you! Delighted you found my article even before I announced it on fedi
https://social.coop/@smallcircles/116379158584600016
Thus far my poll on readership found 4 Meh skips. AI vs. long handcrafted thinkpieces: 1 - 0?
We'll see. Finding that out is also SX, after all.
@smallcircles heh, I thought I had missed the Fedi announcement because it was already there
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login