@jarey thanks for pointing out that plugin. I had misinterpreted it's functionality before. When I saw "Max upvote weigh (points)" I assumed you could only use that configuration to scale the upvote-to-reputation ratio based on the reputation of the user doing the voting.
For others that run into a similar issue. Using the plugin Jarey pointed out, if you'd like to make 1 upvote = 10 reputation I was able to do that by setting:
Max upvote weigh (points) = 9
Since the default weight is 1 upvote = 1 reputation, and this plug in then adds the additional 9 reputation.
It looks to me like the German translation was intented to be informal. That is what most communities would use anyway and what should be the default. So I would consider the formal language in the recent translation a bug.
I also think the translation could be improved. Most parts are very well translated other parts are not so perfect and a few are just wrong.
I'm also not sure, if there is really a need for a formal German translation. It's just a UI. We wouldn't talk to Siri, Google or Alexa in a formal way.
Of course there is nothing wrong to have a formal translation as an option, but would there be a maintainer? Who wants to do the extra work and keep the two translations in sync.
Hey, get ready to be confused @frissdiegurke -- there's a third type of hook, rounding out the behaviours 😆
action hooks are, as @Mega describes, fired when something happens, and NodeBB doesn't care about the response.
filters are fired when plugins might change things. The majority of hooks in NodeBB are filters.
static hooks are fired when you need NodeBB to wait until your plugin is complete in order to do something. There is only one static hook available right now: static:app.load, which is fired on startup.
In this case, since the post is already slated to be deleted, but you want to do something before it is deleted... we may want to consider adding a new hook called static:post.purge.