I often see the "Robustness Principle" invoked when discussing ways to improve #ActivityPub interop. There's an IETF draft that discusses the negative consequences of this strategy. Instead, they suggest that "A community that takes an active role in the maintenance of protocols will no longer need to rely on the robustness principle to avoid interoperability issues." Sounds great to me.
https://intarchboard.github.io/draft-protocol-maintenance/draft-iab-protocol-maintenance.html#name-harmful-consequences-of-tol
Conversation
Notices
-
Embed this notice
Steve Bate (steve@social.technoetic.com)'s status on Friday, 29-Dec-2023 02:32:55 JST Steve Bate -
Embed this notice
Evan Prodromou (evan@cosocial.ca)'s status on Friday, 29-Dec-2023 03:27:36 JST Evan Prodromou @steve I guess it comes down to how important communicating with people is, versus how important having a readable protocol spec is. I'd rather have lots of people on the fediverse, on lots of platforms, than satisfy the aesthetic requirements for specification readers.
In conversation permalink
-
Embed this notice