I like to do clean installs. It's nice to start over with a "clean slate". I consider reinstalling as part of what one might call "computer hygiene". If, by chance, I managed to pick up a rootkit or other form of malware, reinstalling should help me get rid of it. I also use dd to (very carefully) wipe the MBR in case something nasty is hiding in there.

Reinstalling is definitely a pain, but I have an idea for a system that should make it much less painful. I will install Devuan in a VM and configure it exactly the way I want it. Then I will use refractasnapshot to create a live DVD ISO file that can then be used to install the new version of Devuan.

This VM will never to be used to do anything other than create customized Devuan ISO files. And every time a new major version of Devuan is released, the VM will be dist-upgraded and used to create a new installation ISO file.

Since I use cheap phones that don't allow the bootloader to be unlocked, I basically gave up on the idea of using a custom ROM, even one that I've customized myself. Sadly, even my Motorola (Moto G Stylus 5G 2021) phone won't allow the bootloader to be unlocked because it was made for Tracfone.

That being the case, the Universal Android Debloater seems like my best option:

Universal Android Debloater
https://xdaforums.com/t/2022-07-03-v0-5-1-universal-android-debloater.4069209/

Universal Android Debloater Next Generation
https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation

I prefer to not use Google Authenticator, but to use a different program instead, like Aegis Authenticator. Unfortunately, it apparently only runs on Android.

For what you are ultimately trying to accomplish, I think that a better solution would probably be to use a program like numberstation or Gnome Authenticator.

The problem of files mysteriously disappearing is still an issue since I recently had another one disappear. I was beginning to wonder if the HDD is going bad, so yesterday I analyzed it using smartctl. Other than some occasional ICRC errors, the drive appears to be healthy. The ICRC errors suggest that the SATA cable may be bad or loose, though, so I am going to replace it soon.

Unreliable electrical power is a problem where I currently live. There are frequent, short power failures here, especially during storms and on windy days. Could this be causing my documents to disappear? Although power failures can cause data loss, I doubt that this is the cause because the files were not being written to when the power failures occurred. In fact, I don't think the files were even open. So, unless I am wrong about this, it seems that the cause of my disappearing documents is still a mystery.

Take a look at this:

Package: bilibop-lockfs
https://packages.debian.org/stable/bilibop-lockfs

It's intended to be used for external media, but can probably be used for internal drives as well.

There is also uBlock Origin Lite which does work in Edge and the newer versions of Chrome/Chromium.

When I have some time, I will attempt to build an installer ISO. Not quite eight years ago, I built several live CDs. Maybe what I learned from those experiences will be helpful.

This website is likely to be very useful: https://snapshot.debian.org/

It appears that some very recent packages can be found here:
https://snapshot.debian.org/archive/debian-security/20250101T021323Z/pool/updates/main/l/linux-6.1/

You may be in luck. I stumbled upon this yesterday and saved the info because it looks like it could be very useful:

The Free Software Media System | Jellyfin
https://jellyfin.org/

@stargate-sg1-cheyenne-mtn

Thanks for the tip.

Live streaming seems problematic to me if the sessions are announced in advance publicly since this lets potential adversaries know when to carry out their attacks (or attempted attacks). If possible, coordination should be carried out using encrypted chat (including encrypted voice calls), rather than using insecure communication methods like email, public websites, regular telephone calls, and SMS text messages.

Some resources that may be useful:

PRISM Break
https://prism-break.org/en/

Security & Privacy Evaluations
https://madaidans-insecurities.github.io/

Rob Braxman Tech
https://rumble.com/c/robbraxman

An idea just came to me, so I went ahead and tried it:

$ aptitude why libc++1-16
i   atril                Depends libatrilview3 (= 1.24.0-1+deb11u1)
i A libatrilview3        Depends libwebkit2gtk-4.0-37 (>= 2.5.3)   
p A libwebkit2gtk-4.0-37 Depends libc++1-16 (>= 1:16.0.6)          

$ aptitude why libc++abi1-16
i   atril                Depends libatrilview3 (= 1.24.0-1+deb11u1)
i A libatrilview3        Depends libwebkit2gtk-4.0-37 (>= 2.5.3)   
p A libwebkit2gtk-4.0-37 Depends libc++abi1-16 (>= 1:16.0.6)       

$ aptitude why libunwind-16
i   atril                Depends libatrilview3 (= 1.24.0-1+deb11u1)
i A libatrilview3        Depends libwebkit2gtk-4.0-37 (>= 2.5.3)   
p A libwebkit2gtk-4.0-37 Depends libunwind-16 (>= 1:16.0.6)

So, apparently the new packages are dependencies of libwebkit2gtk-4.0-37. That's a new one for me. I did not know that packages could suddenly acquire new dependencies. Perhaps this is just one of the oddities that can show up when one is running oldstable.