Comment on Discussion: Long-term need for automation tools for moderation
MentalEdge@sopuli.xyz 3 weeks ago
If everything is a priority, nothing is a priority.
By now I’ve written four bots using the lemmy API.
Any one of your ideas is doable in a weekend if I ever feel then need for a modding bot. But I haven’t.
Honestly that’s how it should be. Modding can have such diverse needs depending on community that just implementing every possible eventuality into lemmy itself, is a huge ask.
Any large community on discord, reddit and other platforms, make extensive use of automod bots. Because using the API, you can write bots that do whatever you can think of.
Modding is volunteer work, but it is work.
If you need tools, find them. If they don’t exist, create them. If you don’t have the skills or time, then don’t volunteer.
There are a lot of people who make excellent mods who are not programmers. It’s already a small enough pool that requiring a particular skill only further narrows the pool. It also has a secondary effect that good mods may be unwilling to take on larger communities, or additional responsibilities.
If we want better moderation, the fediverse has to become more friendly to non technical people.
That’s not what I’m saying.
Obviously not everyone needs to code. Once I write a bot, it could potentially be used by anyone.
Only a small percentage of mods need to also be developers. But since that group isn’t big enough yet, the solution is growth.
Not asking the platform devs to do even more. They too, are volunteers.
Fair, thanks for the clarification.
To be clear, I’m not personally thinking about Lemmy here specifically. But in any case, however its done - either via the settings, or an easy to official or officially endorsed mod-bot - access to these tools should be easy and well-known for community owners.
If you need tools, find them. If they don’t exist, create them. If you don’t have the skills or time, then don’t volunteer.
Not every would-be moderator of a community has the skills or knowhow to make and/or host these things. Even Reddit now, at its size, lacks some capable tools not consistently covered in automod tools.
I’m not against any of that.
What I disagree with is that this is a priority. It’s a nice-to-have.
Once mod actions are supported, and an API exists, any imaginable automation can be implemented by anyone with impetus to do so.
As such, the priority of further integration drops drastically and platform developer attention can and should move elsewhere.
Mod tools are best created by the people who use them. Even better when they are created for the needs of a specific community. As such, more advanced features should be deferred until later.
Once communities grow large enough that there are a signifucant number lf moderator-developers, it might be worth creating a generic bot that can be configured as meeded. (As have happebed with reddit, discord, etc.)
Asking for these tools before then, is inefficient, because the people who ideally should be working on it, haven’t shown up yet.
Well I’m thinking in terms of how to ‘shore up’ the fediverse, so to speak. I do think all of the examples in my OP that I’ve given are pretty general and one or more of them would be implemented by most communities the moment they were able to do so.
wjs018@piefed.social 3 weeks ago
In Skavau’s defense, they aren’t a programmer, but are probably one of the most active people on piefed’s chat server/matrix room as well as the codeberg repo providing ideas and feedback. So they are volunteering time that way (in addition to being site staff for piefed.social).
Some of the ideas in this post are good imo, but are currently not possible yet using the piefed api due to it being much less complete compared to lemmy’s. So, it helps us figure out prioritization on what kinds of endpoints would be useful to flesh out next.
MentalEdge@sopuli.xyz 3 weeks ago
Indeed.
My core point is that when it comes to moderation, I would prioritize actual mod actions (such as a mod being able to mark posts nsfw instead of deleting them outright) and API support for those actions, over built-in automod features.
Once you have an API, anyone with the skills can implement whatever automation they need.
After that, I would priotize a bunch of other things, too, before ever coming back around to built-in automod features.