However, the complexity is unavoidable in a decentralized network. A standardized representation of a quote (FEP-e232) was proposed long time ago. It was easy to implement, versatile (FEP-e232 could be used to build any kind of link, not just a quote), and it was supported by a significant number of fediverse projects. Then Mastodon developers decided to invent a different kind of quote, with all the unnecessary complexity that you described. But I'd rather deal with this complexity than have some centralized standards org telling me what to do.

Another issue is disinformation -- and that is really weird, and unique to Fediverse. You probably heard that JSON-LD is required, but that is not true. The spec doesn't require it. Only a few Fediverse projects actually use JSON-LD, and as a developer you don't need to worry about it -- adding "@context": "https://www.w3.org/ns/activitystreams" to your JSON makes your software compatible with >99% of Fediverse instances, and even that is only necessary because Mastodon has a bug. Unlike the problem of competing standards, this problem can be solved by writing better documentation.

Hey, thank you! Delighted you found my article even before I announced it on fedi

🫧 socialcoding.. (@smallcircles@social.coop)

#ThoughtProvoker 🤔 #fediverse is at an inflection point. Either revival and course correction to the original #ActivityPub protocol power and promise. With the potential to #ReimagineSocial. Or keep current track with fedi-we-have. Be content with a few great and reasonably popular app platforms. Surely some more to come. But with a messy wire protocol that stifles #innovation and isn't future-proof. #AskFedi do you dare to dream? This special thought provoker is based on personal reflection and 8 years of #commoning. Deliberately exposed to the inherent unsustainability of the #FOSS movement. Burning privilege by spending my savings. Goal: 1st-hand experience to learn the #social dynamics that make a #commons tick. I invite you to a #brainstorm & #ideation ride. To ponder how #fedi can organically evolve. Become unbeatable by #hypercapitalism. https://coding.social/blog/grassroots-evolution But in an age of #AI who still reads long handcrafted #blogs? Fill in the #poll. #SX #SocialCoding #SocialWeb [ ] In the end I more or less read the whole article [ ] I read the article summary, skimmed for highlights [ ] I passed the problem section, read the tech ideas [ ] Meh, skip. Too technical. Too social fluffy. Other

social.coop (social.coop)

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.

* 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

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