343
Lemmy's Image Problem (Updated 02-06-2024)
(wedistribute.org)
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
Instead of playing the blame game, let me see if I can help with a solution: I am fairly certain that I can take the "admin" functionality that I built for fediverser and use it as the basis for a "moderation dashboard". It's a Python/Django application that can communicate with the Lemmy server both through the API and the database. The advantages of it being a "sidecar system" instead of being built "into" the Lemmy code itself is that I am not blocked by any of the Lemmy developers and the existing instance owners do not need to wait for some fork to show up.
I can propose a deal: at the time of writing, there are ~200 people who upvoted this article. If I get 20 people (10% of the upvoters) to either sponsor me on Github or subscribe to my Europe-based, GDPR-subject suite of fediverse services, then I will dedicate 10 hours per week to solve all GDPR-related issues.
How does that sound? To me it sounds like a win-win-win situation: Instance admins get proper tooling, Lemmy devs get this out of their list of concerns and users get a more robust application for the fediverse.
I wish you the best of luck on this and I truly hope you do this, but this is what the lead dev of Sublinks tried to do. That's the missing piece here. He tried making an external mod tooling system. Maybe you'll have better luck than he did. I really hope you do.
That sounds great! Be sure to get in contact if you run into any problems or limitations with the API.
In a similar vein, I've seen a lot of auto moderator implementations created. If instead of creating yet another project, people started contributing to existing ones we'd have a good core set of functionality that could be shared across instances. Competing implementations are fine, but at some point the efforts get spread so thin that progress is limited.
This sounds great!
Glad you agree, and hope to see your name on the sponsors list and/or the communick signups. ;)
If someone will point me there I'm on it.
The links are on the first comment:
Ok! Amazing.