And it was suggested that I move this conversation to the open-store group. Sorry for posting it in the wrong place. So no worries if you don't address this during the stream.

@RJDan hmm, i may be able to do something about syncing passwords, but it would require cooperation from the UT development team. no promises though I already have my plate full with the upcoming rewrite of uWolf for Noble and NixManager plugin for lss (which i'm waiting on a test device so i can start working on the UI)

@jezek I'd like to try the 20.04 too . I made a new topic to share the experience...

If I understood @fredldotme correctly there will be a stable release of Dekko2 before/with noble - did I understand him correctly??

Hi everyone , Thanks for a all contributors and for answering questions. From my understanding, in an encrypted device, the phone is really secure after turning it off and before the first decryption/unlocking (BFU), after the device is first unlocked/decrypted (AFU) it is not as secure even if it is locked again because the encryption keys are stored in RAM. For extra security, would it be possible and hard to implement an option in the encryption settings to make the phone like in BFU every time the phone is locked ? Even if it takes longer to unlock each time of course

@UBportsNews Hello. Still happy thanks to Ubuntu Touch. I've done a few snap tests. For KeePassXC, I couldn't get it to work: keepassxc ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. qt.qpa.plugin: Could not find the Qt platform plugin "ubuntumirclient" in "" qt.qpa.wayland: Creating a fake screen in order for Qt not to crash The Wayland connection broke. Did the Wayland compositor die? I just wanted to highlight an interesting post, I think, from the forum that suggests listing applications that work well under UT: https://forums.ubports.com/topic/11143/snaps-tested A huge thank you to all those who contribute to the life of UT!!!!