Frederik Ring

I think I was missing an important detail in my comment about that "Plus" feature above: back then users still could dismiss the consent banner without making a consent decision....

Thanks for following up on my reply. I agree with basically all points you mention, and I think it all of this comes down to answering a single question. ##...

> For example: I could build a plugin to handle client-side error monitoring. The plugin would only be executed in the browser by Offen, if the user provided consent. The...

> Lighthouse support would also be a great way to foster adoption. That sounds good, I haven't thought of it yet. I wonder if it'd be possible to do this...

It'd be relatively urgent to translate at least the opt-in banner in order to enable non-English websites to run Offen in a GDPR compliant manner.

> Offen supports multiple languages but is set by default in the instance. We initially did this so that we can make sure the consent UI and the language in...

How would you want to handle the consent banner in such a setup?

Let me try thinking through how that could work: - in case the operator wants to serve a non-default (default as in what's set in `OFFEN_APP_LOCALE`) the script tag is...

@dhenry123 I started working on this in #720. There are still some details to figure out, but if you have any further feedback please let me know. In any case...

@hiensarahly Thanks for letting us know and also for all of the effort you put into that. I created a [branch](https://github.com/offen/offen/tree/vi-locale) for setting this up and testing it. Once we're...