Friendly reminder: last year I built FediMod FIRES, a protocol and reference server implementation for sharing moderation data.

[thisismissem@hachyderm.io]

@the_moep yeah, it's been difficult to get the word out because I don't have a particularly large following.

[Guest]

Thanks for the reminder @thisismissem it slipped through my radar last year

Will try to have a look at it for potential use with Friendica!

[renchap@oisaur.com]

@thisismissem probably not very helpful for now, but we intent to implement *lists (blocklists, email blocklists…) synchronisation in Mastodon in our next version.
We have not defined the exact scope yet but I want it to support FIRES (likely in addition to ingesting « simple » CSVs)

[julian@fietkau.social]

@thisismissem Who would be the target audience for FediMod FIRES? Is it anyone who moderates a fediverse server, or are you looking strictly for admins who can set up software integrations? Is there a minimum server size or moderation workload?

Is anything about it limited to Mastodon or is it applicable to all or most ActivityPub social platforms?

(🫢 Don't tell anyone, but I already know the answers to most of these, I just think it would be helpful to know for others reading this thread.)

[thisismissem@hachyderm.io]

@julian target audience is people producing moderation datasets, that's who'd run the servers.

The protocol can be consumed by any client then, which would likely be instance operators. It's generic not mastodon specific, it's a side protocol to ActivityPub, but uses similar concepts.

It could even be used with AT Protocol (though no one has tried that yet)

[draeath@infosec.exchange]

@thisismissem @jerry spreadin' the word, sounds very useful

[the_moep@mastodon.de]

@thisismissem I took a quick look at it and there are two things I'm wondering about:

• Can this already integrate with Mastodon's FASP? If not, is that planed?
• How are identities of moderated actors/instances as well as the moderating instances protected? As far as I can tell all of that information seems to be provided in clear text which imo would result in retaliation actions being taken against the people putting an instance on the list. Something like this has happened in the Minecraft community on global banlist projects and seems to be (in a lesser form) an issue with Bluesky's public blocklists as well. (And in the email-space Spamhaus gets attacked a lot as well)

[pbaesse@bolha.one]

@thisismissem very nice

[mxfraud@tabletop.social]

@thisismissem I'm going to try to say this with the most respect for you and your work.

If it is not in mastodon mainline as a feature, it might as well not exist.

The problem has never been ideas, protocols, or implementations, its always been adversarial relashionship from gargron and or the Mastodon GMBH leadership team.

They clearly do not want to prioritise this feature and many other feaures that people asked for years (hello local only post).

And the only people that can use this servers are: re-implementers, people that need a dedicated service to scale (and probbaly have multiple, high traffic instances), and hobbyist self hosters.

All the people using masto.host/ 3rd parties won't be able to use it.
Which I assume is the vast majority of the people wanting to have access to that feature in the first place.

Unless Mastodon GMBH start to listen to their community (instance administrators), the complaining will continue I'm affraid.

Again, trying my best here to convey that the work you did is needed and appreciated, and that my problems are with the people holding the power here.

[thisismissem@hachyderm.io]

@the_moep okay, a lot of questions!

1) FediMod FIRES is not related to Mastodon's FASP protocol. You shouldn't need an active connection to a FIRES server to process incoming activities.

2) Moderation data is shared publicly. Your server needs a copy of that data in order to take action. Moderation data providers can share as much or as little data about their operations as they desire.

3) The only way to not make the moderation data clear text would be by using Differential Privacy, and I absolutely do not have the cryptography knowledge to implement that.

4) Private datasets have been requested as a feature. Need to figure out access control. Existing datasets are all public.

Hope that helps.

[thisismissem@hachyderm.io]

@the_moep FediMod FIRES is more parallel to Bluesky's Labeler infrastructure rather than blocklists

[thisismissem@hachyderm.io]

@mxfraud it sounds like Mastodon may be adopting the protocol, and there is other fediverse software out there besides Mastodon. But I also get your frustration.

Renaud Chaput (@renchap@oisaur.com)

@thisismissem@hachyderm.io probably not very helpful for now, but we intent to implement *lists (blocklists, email blocklists…) synchronisation in Mastodon in our next version. We have not defined the exact scope yet but I want it to support FIRES (likely in addition to ingesting « simple » CSVs)

Oisaur (oisaur.com)

[globalvote@mastodon.social]

@thisismissem Https://1024terabox.com/s/1lPj_-RookDKVFmqLkZgryg

[andrew@mastodon.furrow.me]

@thisismissem can I theoretically use this as a housekeeping tool for blocking all ActivityPub nodes of a certain type, e.g., Lemmy, Piefed, Gotosocial, or is there an easier way to do that? How about blocking all users with blank pfp?

Thanks

[thisismissem@hachyderm.io]

@andrew it's not designed for that.

For automatically moderating profiles with no avatar, it'd be as your server learns about them, which could be done using a rails script for mastodon.

[andrew@mastodon.furrow.me]

@thisismissem thanks!