Tempted to write a "What is Fedi" blog post explaining how wanting to have builtin automated blocklists and "trust and safety" features won't fly with almost every Fedi server dev out there. So I can then send it to every post I see about users wanting this and get yelled at for being XYZ.
Timeline
Post
Remote status
Context
8
@phnt Aren't those features already in the process of being added to almost every fedi server? GoToSocial and a number of others already have block list subscriptions
@silverpill GTS can do it by I think importing remote CSV files, Mastodon has their FIRES grant. Those are the only two implementations I'm aware of doings this and they are nothing compared to tens of others. If you don't account for install base that is.
@phnt There is more
The first that comes to mind: https://github.com/Automattic/wordpress-activitypub/blob/trunk/includes/class-blocklist-subscriptions.php
I remember seeing other devs promising to implement automated import
@silverpill Did you know that this apparently exists?
https://github.com/swicg/activitypub-trust-and-safety/
https://github.com/swicg/activitypub-trust-and-safety/
@phnt Yes, this is probably the most active SWICG task force, they even got funding from NLNet recently: https://github.com/swicg/activitypub-trust-and-safety/discussions/144
@phnt The work plan seems to be relatively benign, though:
GtS interaction controls, flagging, blocking, best practices.
Automated filtering was voted down.
@phnt By the way, I found a fun way to sabotage those task forces. You can publish a FEP describing some mechanism (e.g. interaction controls), and say that it is patented. No one in fedi would give a shit, obviously, but this seems to be very important for those working at W3C
Replies
0Fetching replies…