Bryan Redeagle (@bryan@soc.redeagle.me)
Föderation · Mi 07.08.2024 04:53:59
I'm surprised that no one has used ActivityPub to federate block and allow lists. All they are is a collection of actors. Even the instances themselves could be classified as a Service (which is a type of actor).
#ActivityPub #federation #fediverse
Emelia 👸🏻 (@thisismissem@hachyderm.io)
Föderation EN Mi 07.08.2024 12:38:45
@bryan @smallcircles I did look into the viability of this, but ultimately decided against it due to addressing issues and lack of appropriate activity & object types — would've basically been inventing an entirely new vocabulary on top of AP.
Bryan Redeagle (@bryan@soc.redeagle.me)
Föderation · Do 08.08.2024 18:19:54
@thisismissem@hachyderm.io @smallcircles@social.coop It seems like it could be as easy as a collection of actors on another field like following currently is. It would break the spec, but a few fediverse apps do that already.
Evan Prodromou (@evan@cosocial.ca)
Föderation EN Fr 09.08.2024 05:06:30
@thisismissem @bryan @smallcircles that's absolutely the right thing to do! It's an extensible protocol. Also, I think the `Block` activity is fine for this situation.
Emelia 👸🏻 (@thisismissem@hachyderm.io)
Föderation EN Fr 09.08.2024 06:46:12
@evan @bryan @smallcircles right, but AP actually didn't add anything at all to the data I was looking to model, and could've actually been an easier attack vector.
AP works for social data, but not really for moderation data which in information sharing tends to be more broadcast rather than send & receive.
See my other note in this thread about why `Block` isn't actively used by much