Do NOT create out-of-bound custom and app-centric mechanisms that define new and expected behavior on protocol level.
https://codeberg.org/fediverse/fediverse-ideas/issues/33
#SX #SocialCoding #SocialWeb #ActivityPub #ProtocolDecay #Botiquette
Do NOT create out-of-bound custom and app-centric mechanisms that define new and expected behavior on protocol level.
https://codeberg.org/fediverse/fediverse-ideas/issues/33
#SX #SocialCoding #SocialWeb #ActivityPub #ProtocolDecay #Botiquette
cc @evan relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.