ArchAengelus
Wait til your table with all the checksums gets messed up on an “older” btrfs install. Happened to me on a VM because I didn’t know copy-on-write should be disabled for large frequently partially updated files. It also slowed that VMs IO down a lot.
Like most file systems, BTRFS is great if you know the edge cases. I recently moved to ZFS on my new work system, which has been a great change in terms of in-line snapshots and the like.
If EXT4 meets your needs, that’s awesome. If you understand how to use a different FS well or are willing to learn (and risk), I would also encourage other options as well.
Love the comics.
Small feedback: could you make the text a little bigger relative to the image? On my tiny phone I have to zoom in to every panel individually to read it.
The register simply says “nothing to see here” 😂
No matter how good the protocol or client encryption, your privacy is only as good as your own physical security for the device in question.
Given that if you lose your private key, there is no recovery, I would be surprised if there were real back doors in the clients. Maybe unintentional ways to leak data, but you can go look for yourself: https://github.com/signalapp/Signal-Android
They have one for each client.
I feel your pain man. Our university of 40k people did the same thing “from on high” and we ran into the same problems in our lab. We only had 4 million files to move into a Teams share. Which, btw, takes about 5 weeks to “sync” to OneDrive, which is how we were expected to replace our workflow instead of a shared network storage drive our lab owned
q_q