Can you make the bot crawl the mod/admin actions too?

[M4rtineski]

• "ModRemovePost"
• "ModLockPost"
• "ModFeaturePost"
• "ModRemoveComment"
• "ModRemoveCommunity"
• "ModBanFromCommunity"
• "ModAddCommunity"
• "ModTransferCommunity"
• "ModAdd"
• "ModBan"
• "ModHideCommunity"
• "AdminPurgePerson"
• "AdminPurgeCommunity"
• "AdminPurgePost"
• "AdminPurgeComment"

This would ensure that a moderator didn't do anything behind your back. And admin actions would just be included alongside as a bonus thought it wouldn't be useful unless the admin takes action without anyone making a report.

E: Moving this to the top for better tracking:

"This is the list of modlog actions we can check for. I've bolded the ones which might be of interest."

[M4rtineski]

Tracking modlogs can be difficult when you moderate a few communities.

[chris-y]

I can't see anything in Pythorhead about reading mod logs. I'll have to see if there's an API for it.

[M4rtineski]

Shouldn't there be an API for it if lemmy is open source and has lots 3rd part apps? Or APIs for this and bots are different things?

[chris-y]

This looks like the API for it:
https://join-lemmy.org/api/interfaces/ModlogListParams.html

Need to figure out how to add that to Pythorhead.

[M4rtineski]

Have fun working on that while I go through my burnout. I could be back tomorrow or in a few days...

[chris-y]

The API is actually GetModlog, I'm not sure what that other one does (the documentation is terrible).

Anyway, I've added it to Pythorhead - PR 109

We'll need to call it for each community we're interested in, and keep track of the logs we've seen.

[M4rtineski]

For this specific issue other things like community transfer, mod appointemts, mod removal and so on would be useful too but I assume declaring what should be read will be trivial.

Maybe a way to set the crawled actions per community or give a community it's specifc set of actions while the other ones share one? Because for example lemmy directory does a lot of locking. Otherwise we could give up this specific action for them all which wouldn't hurt much. Especially when the shared modlog is on the horizon, the point is to notice quickly if appointed mod goes rouge or if there was an action taken to give a second opinion. With shared modlog it will be easier to keep a tab on it but notifications will help with a fast response time.

[chris-y]

PR merged, available in 0.31.0

[chris-y]

For this specific issue other things like community transfer, mod appointemts, mod removal and so on would be useful too but I assume declaring what should be read will be trivial.

It looks like we can get everything, or just one thing. If you want more than one you need to call it multiple times (which probably isn't that annoying, as all the actions appear to return slightly different responses anyway)

[M4rtineski]

I moved the checklist into the issue but it didn't get detected as a part of the issue? Could it be the sub-issue blocking the task progress functionality? Anyway, should be easier for you regardless with it at the top.

[chris-y]

Not sure. You can convert the list items to sub-issues by clicking on the menu next to them but not sure we really need a sub-issue for each.

[M4rtineski]

I was talking about this visual thing for showing how many tasks are completed that you can see from the issues list view. Not important but it was partially why I did this and didn't expect it to not show up.

[chris-y]

It might be because there's a "task" sub-issue already associated with it.

[chris-y]

Actually, no, it's working here:

[chris-y]

...only on mobile though, on the web it doesn't. Weird.

[M4rtineski]

...only on mobile though, on the web it doesn't. Weird.

For me it's neither.

[chris-y]

Do we need notifications for pinning and locking?
Transfer might be worth having?

I'm not sure what these are for: "ModAdd" "ModBan" "ModHideCommunity"

AdmnPurge* probably isn't all that useful

[M4rtineski]

Pinning and locking would only make sense if we had exclusion logic for the directory community. The potential of abuse and the relevance of those actions are very low so we can skip it as it's not worth the trouble.

Transfer is a big action worth noting but I think we would notice that if any of us or the bot was unmodded or if someone new was modded. The only situation where it would be useful that comes to my mind is that if we're mods at someone's community and the community gets transferred to an already existing mod that isn't us which is just not going to happen.

Not sure either about those. :x

Admin purge for posts and comments feels like it could be useful to see when an admin had (or felt like) to step in. Unless that's already covered under the mod actions then idk what would that be.

[chris-y]

Ok, need to add unmodding as skipping that currently, but we definitely need to know about it.

[chris-y]

Added unmodding notifications