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.
Post
Remote status
Context
9@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
@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
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.
@silverpill @phnt >Automated filtering was voted down.
Hmm, I see that one of the recommendations from the person who opened this issue includes a proprietary enterprise service. I think that's a major point against it.
https://github.com/swicg/activitypub-trust-and-safety/issues/28
But what I'm more interested in is whether they wants to filter text? If so, wouldn't it be easier to just crudely add a lexicon containing tens of thousands of sensitive words to block users from posting, like some social media censorship? ![]()
@caohuak @phnt I think they are interested in CSAM detection, but once the infrastructure for large-scale filtering exists it can be re-used for whatever authoritarian governments come up with.
Replies
1