rugk

> there should be enough time to properly verify public keys are non malicious and come from a trusted source. Or, the reverse: Enough time for the company to find...

BTW, actually Firefox has even "better" support for it, as they have a proper API for getting the plain-content as it (without required minification). See https://github.com/tasn/webext-signed-pages/issues/16 for details.

That takes way too much UI space. Why not push an update from the Threema app in case this info changes?

I guess it should be not too hard to implement, if you just execute the search in the Threema app. Threema Web just "mirrors" the result then…

BTW, just a wild guess: Some stuff could be kept in RAM for the "restore tab" feature.

Don't know, I cannot say Threema Web even uses multiple GB when it is open. I also don't know how/whether it is possible to measure/display the RAM by it's tab...

At least, now you can use `about:performance` to see the RAM usage of a single tab. So can you all report that RAM usage?

Hmm, at least the background pic is not, anymore. (https://github.com/threema-ch/threema-web/pull/425) But that solution may not be a good one for all things, which can be dragged there.

When will this finally come? I see https://github.com/threema-ch/threema-web/pull/420 is still open…

Maybe not an option, but if you've read your message on your desktop (and really read it, …) hide the notification on your mobile phone, if that is possible.