this post was submitted on 24 Oct 2023
121 points (99.2% liked)

Fediverse

28746 readers
315 users here now

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 [email protected]!

Rules

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

founded 2 years ago
MODERATORS
121
Lemmy Moderation Tooling (modder.lemmyverse.net)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/fediverse
 

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. ๐Ÿ‘

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 1 year ago

Currently, it's only storing your Lemmy JWT token (if you chose to save it) and your site/user data.

There's not really much value in saving these since there's no user configuration stuff yet, providing more of a risk if these tokens were leaked (potentially for global admins)

I was thinking of implementing a way to share data outside of Lemmy (for mod notes, ignored reports, user "Strikes", and potentially user config). If this was not purely a frontend (and I had some kind of DB backend) then this would be less of a concern.

I didn't really want to run a backend, since it would involve me storing data on users of the tool - But this would be an option for people that set this up in their local Docker.