thinking about that time where i suggested an extension to AP to allow people to collaborate on blocking/mute lists, and how a bunch of freeze peach people got mad about it, and how the other platform has this as a first class feature

[ariadne@social.treehouse.systems]

thinking about that time where i suggested an extension to AP to allow people to collaborate on blocking/mute lists, and how a bunch of freeze peach people got mad about it, and how the other platform has this as a first class feature

[aurelia@social.treehouse.systems]

@ariadne I haven't validated this idea, but I did think about building a very tiny webapp that you can oauth grant some permissions to as instance admin and then sync up blocklists from, like a minimal blocktogether.

and one could build it without anyone knowing it exists until it's there.

[ariadne@social.treehouse.systems]

@aurelia my point is that we know "what" we need to build in order to make activitypub successful in the mainstream, but that some others do not want it to be successful, and thus try their best to derail any efforts to change the status quo

[aurelia@social.treehouse.systems]

@ariadne i hope so, but i wouldn't say that i know.

because in my experience, some people are just not exactly... measured... in their moderation style. delegated trust only works if you're very explicitly informed about who you give that trust. and with the current instance model it's not trivial to change as a user either.

(i'm very happy on treehouse)

this is a very biased perspective from my miserable time as a small time instance admin, but shared blocklists have the potential to amplify that too.