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

I haven't yet been able to get anyone to adopt it or even signal intent to adopt. But regularly I see people complaining about the lack of data sharing when it comes to moderation, especially for combating spam, scams, and harassment. The tool is there, please use it!

Whilst I'm not actively working on FediMod FIRES this quarter, I did apply in November for a grant to continue that work, and last I heard a few weeks ago is that the grant made it to the next stage, so I may have some money again to fund development.

It's not 1.0.0 yet, because I decided it needed more work for me to be happy to call it that, but it is usable!

Installation is also super simple for data producers, literally two commands on debian or ubuntu boxes.

Learn more: https://fires.fedimod.org/manuals/reference-server/

#moderation #fediblock #administration

FIRES Reference Server | FediMod FIRES

Fediverse moderation Intelligence Replication Endpoint Server

FediMod FIRES

@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.)

@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)