@alex @MichalBryxi @evan
> The NoBot isn't app specific fwiw, it's pretty standard.
"pretty" boils down to de-facto standard, or rather it became a sorta kinda requirement by means of post-facto #interoperability. In other words: Who comes first, and popularizes some custom app-specific extension, becomes owner of that part of the spec that is now considered protocol-native.
#NoBot is app-specific too. Or Microblogging domain-specific perhaps, albeit implicitly then.
When it comes to considering it standard, we talk about accepting #ActivityPub protocol decay. Specifically:
- Considering the way account profiles are handled to be part of the protocol.
- To handle special control words (or just #NoBot) in the profile text.
Attached: 1 image
I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText
See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828
Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org
Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498
@ben@werd.social
#SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse
social.coop (social.coop)