Hey! The site-memory system was honestly a buggy mess in the older version. I originally built it for myself and left it half-finished. Seeing the usage, I made a v2.0 overhaul completely rewriting everything. If you give it another shot, it should work exactly like you expect now. Thank you for testing it out and I apologize for the first version.

So sorry about that. I originally built this tool just for myself and ended up leaving a really messy localized bug in the old code that accidentally forced German on some users. Since people are actually using the extension now, I just dropped a massive v2.0 overhaul that completely fixes the language settings and rewrites the whole system. If you try it again, it should actually be in English (or whatever your browser language is, if it doesn't include that language, let me know) and work smoothly. Thanks for the feedback!

Thanks for the feedback! The older version didn't include any translation since I didn't think of that sadly. I did just push a new completely rewritten v2.0 that includes a language system (with English :>), so all the menus and settings should be fully in English now.

Thank you for the detailed feedback! Regarding "Speak Selected" and Firefox Reader View, these features use the browser's internal "Web Speech API" which generates audio outside of the standard HTML5 media elements (like those used by YouTube). Because this audio is handled by the browser/OS level directly rather than through standard media tags, it is currently impossible for my extension to intercept or control that specific audio stream (unless they add an Intercept API for that). I apologize for the limitation, it is a restriction of how Firefox handles these accessibility tools :(

Hey, thanks for the update! Glad to hear the storage and German bugs are gone. I see what you mean about the built-in volume enforcement. That was a leftover code snippet in my code which caused a back off enforcement which tried to apply the volume every time the websites sends any mutation (an element changed) events. I'll write a hotpatch right now to fix this issue, which will apply the volume (if set) once on website loading, then prioritizes the user's input. v2.0.2 should be published pretty soon (next couple of days).

Original Reply: Thanks for reporting this! The older version had a couple of bad bugs that broke storage saving and forced the German layout on people because it completely lacked a proper language system. Both of those issues have been fully fixed in the new v2.0 overhaul I just published. Feel free to give it another try, and I'd love to hear your feedback!