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

Great concept - more transparency on why some domains get added to a denylist, and by whom, was sorely missed. That should go some way towards avoiding arbitrariness in managing those lists (looks at thebadplace)

@gotofritz funnily enough, FIRES was created iniitially as a concept in the context of Are0h's FSEP paper, I wanted to solve the "How do we share this data in a generic, non-thebadspace specific way"

https://nivenly.org/docs/papers/fsep/

Federation Safety Enhancement Project (FSEP)

With the surging popularity of federating tools, how do we make it easier to make safety the default?

The Nivenly Foundation