Very true, though as a moderator, I expect you’d need to validate the report is not reporting something that’s totally fine.

I’m not sure how to deal with this, perhaps I could read your user settings for blur_nsfw and apply that as the default? Or, perhaps a toggle setting that just turns media embeds on/off completely that defaults based on the same user-setting?

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 😁

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

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…

That would be great!

In what language is it written?

JS wtih React and MUI Joy

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.

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.

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.