@pixelfed This seems like a bad idea. We already have the Fediblock list, which is supposed to weed out bad actors, and it's already seen a lot of scope creep, for better or for worse.

The Fediverse is supposed to be decentralized, and centralized moderation completely breaks that model.

@pixelfed

https://www.moddb.com/

@pixelfed How would moderators access the database without letting bots access the blocklists? On the Mastodon side, instance admins already have to hide blocklists from web scrapers like FBA bot, so a database of blocklists is a an all-you-can-scrape buffet for these bots unless specific measures are taken to prevent this.

@pixelfed meanwhile on #calckey

@pixelfed I have concerns about this :

It seems to add centralisation
Block lists have already proven highly problematic due to individual blocking policies and a high number of errors
There seems to be a growing lack of focus at Pixelfed with projects being started but never quite finished (eg the app, which should be the main way to access Pixelfed, is languishing in Beta lacking many facilities and basics)
The name ModDB already exists and is likely to cause confusion

@pixelfed you should rethink that name.

@pixelfed The #crowdsec approach? Naiss.

@pixelfed don't use this name.
When you say ModDB, only one site comes to mind:
https://www.moddb.com

@pixelfed good thing federated techies and gamers don't overlap much or this name might confuse people about its relationship to https://moddb.com

@pixelfed Someone tried this with Minecraft and it didn't work well. What safeguards does this system have against abuse?

@pixelfed
Hi, my two cents regarding the name, there is a moddb.com (and also indiedb.com, but that's not really relevant in this situation).
That site contains game mods, all kinds of them, and exists who knows since when.
Just saying.