Somehow to store shared-moderation data (ie. user mod notes, strikes, etc)

[tgxn]

There needs to be a way to store/share data between the moderation team of specific instances. This would allow display of additional data in ui:

• User moderation comments
• user moderation history (ie. previous bans, content removals)

[tgxn]

I'd rather not run any DB's - There could be a place to run a DB store along with #50 when instances host their own container with lemmy modder.

[Pdzly]

Hmm interesting! I could imagine, that admins could have their own admin settings, where they can select their database or api. But some sort of backend with a storage is required to save those settings and authorisation of the users actions.

I could imagine either:

1. Having it directly connecting to a database ( sql? nosql?(documentdb like mongodb?)
2. Having a api (software served by you like lemmy-modder-storage-api or so) be hosted from the instance, where the api calls the other api with different methods ( for example POST /notes with the mod note as the body ). This would need a backend too, but then 3rd parties can write the api in different languages and support even more wider storages + custom logic, like slack notifications on mod notes, actions etc.

This is just an idea dump from my side.

[tgxn]

I was thinking redis and express as the backend, had some thinking in https://github.com/tgxn/lemmy-modder/issues/50 on api and backend design

another option is to create a patch for lemmy to support storing modnotes along with users.

[Pdzly]

I did mine with a simple id reference to the report if you want it per user just do a extended reference to the user with the id. I would not count on lemmy devs implementing anything. As the recent requesting of mod tool improvement got denied with the reason "Its good enough". If you are good with redis do it :) I am more in mongodb and ORM, sadly ORM is just a typescript thing. Js is able to do that too but with pseudo Models.