- cross-posted to:
- test
- lemmy_mod_tools@discuss.online
- cross-posted to:
- test
- lemmy_mod_tools@discuss.online
Hey all,
I’m the author of lemmyverse.net and I’ve recently been working on a new moderation tool called Lemmy Modder. https://modder.lemmyverse.net/
Currently, it supports user registration/approvals and content report management. I offer it either as a hosted app (which is currently only compatible with Lemmy 0.18 instances) or a package that you can run alongside your Lemmy instance (using Docker-Compose)
Feel free to give it a go and send any feedback my way :) https://github.com/tgxn/lemmy-modder
Edit for a note: This tool does not save, proxy or store any of your user credentials or data to me, it is only ever stored locally in your browser. I also do not use any website tracking tools. 👍
Is this moderation of any communities on an instance, or any communities moderated by someone who had an account on that instance? Still don’t really understand how federated moderation works.
Would the ideal end goal be to run it on an instance for mods on that instance, like say mod.lemmy.ca ?
Hehe, yeah I have done minimal testing as a community-moderator, I will focus some more time to make sure this also works as expected. As a community-only-moderator, you should still be able to call the APIs that return content reports, limited to your communities.
Edit: I’ve made a bug for myself to look at for validating everything still works as a community mod https://github.com/tgxn/lemmy-modder/issues/62
This tool lets you login as any account, and given the moderation APIs return content, then you’ll be able to see it in the UI. (so normal users would likely only be able to see the moderation log)
At the moment, there’s not really much benefit in running it locally, unless you want to be sure that your moderators are using an “approved version” or if (soon) I have to release a separate package for Lemmy 0.19. In future, I expect to be able to link into the Lemmy/Pictrs databases to get additional metrics/content that’s not available on the Lemmy API, but that’s a future problem :D
That sounds amazing, I’ll keep an eye out for more updates :)