Do you already have a list of features you're planning to implement?

I'm aware there are a lot of requests from admins for certain capabilities, so low-hanging fruit like local user lists are probably on the roadmap already. Just wanted to start hashing out the scope and what everyone had in mind.

Second, what is your/everyone's vision for how this would be implemented?

I started a small side project for a set of tools like this, and I'd much rather combine efforts with some other people or at least contribute meaningfully to their efforts.

My current implementation (if you can even call it that?) is a sidecar container that can be mapped alongside stock Lemmy at a dedicated path like /lemmy_mod_tools. Living under the same domain as Lemmy-UI allows the JWT to be used to seamlessly authenticate into the mod tools component.

My plan is to use the official REST API for everything possible and only query the Lemmy DB directly to fill in the gaps. I'm also trying to avoid any writes to the database if and where possible, but for certain things, it may prove to be unavoidable. I'm also unsure of the implications of directly modifying data in the database, but certain operations seem to be safe. By safe, I mean changing the values won't break anything, and the changes that are made don't need to be federated.

So let's hear your plans ideas, wish lists, etc.