From what little I've poked around with it seems to be a really cool tool! Love to see new moderation tools! One thing I noticed is I can't seem to get it to work with community moderators that aren't site admins, though I'm not sure if that's just me messing something up
No worries, I responded above that most of my testing has been done as a global admin, I need to do further testing to make sure everything is working for community-only mods. ~~Happy for you to create a bug on the GitHub with information on what you're seeing as a community-only mod :D~~
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 ๐
it looks to be working now, thanks!
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 :)
Neat! Any chance you can display the user modlog in there too? So everything can be seen and done from there?
I'd love to be able to have a modlog containing all the entries for a particular user, but the Lemmy API doesn't currently support getting filtered results per user. ๐ I'll have to make an issue for it and maybe an upstream one to add this to Lemmy...
Oh I ask because they managed to get it in photon and alexandrite. Not sure how they did it though
i was wrong - i should be able to do this actually ๐ ... the API seems to provide community and user id filters! I've made a backlog item https://github.com/tgxn/lemmy-modder/issues/75
Nice one!
That would be great!
Great work!
In what language is it written?
In what language is it written?
JS wtih React and MUI Joy
Nice! I already looked into i had some recommendations. Nothing big but small changes
I'm absolutely terrible at nginx. Can you share the config you used for your hosted version?
You could try something like this:
http {
upstream modder {
server lemmy-modder:80;
}
server {
listen 81;
location ~ /myapp {
proxy_pass http://modder;
}
}
}
let me know how you go.
The hosted version is using GitHub pages. I use Traefik for my version so don't have nginx config. I can make task to have a look at this and create an example config, but no promises on when I can do that.
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.
Shoudn't there be some backup on dropbox or nextcloud (or even downloading a text file) for this?
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.
I love that you can see when a report was created! Can reports be sorted by the time they were reported, like oldest to newest (or vice versa)? Or sort by community?
not yet, but improved sorting is on the cards.
the main issue is the lemmy api's don't support most of this, so it'll have to be implemented locally.
for example, ListPostReports only allows: community_id
, limit
, page
, and unresolved_only
as parameters:
https://join-lemmy.org/api/interfaces/ListPostReports.html
PR's need to be submitted to Lemmy core to add this functionality, so for now I do a infinite load as you scroll.
I was wondering if that might be the case. Hopefully future Lemmy updates will allow for this.
Fediverse
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!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world 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