Another aspect is the social graph. It’s targeted for normies to easily switch to.

Very few people want to install a communication app, open the compose screen for the first time, and be met by an empty list of who they can communicate with.

https://signal.org/blog/private-contact-discovery/

By using phone numbers, you can message your friends without needing to have them all register usernames and tell them to you. It also means Signal doesn’t need to keep a copy of your contact list on their servers, everyone has their local contact list.

This means private messages for loads of people, their goal.

Hey, we know this account sent this message and you have to give us everything you have about this account

It’s a bit backwards, since your account is your phone number, the agency would be asking “give us everything you have from this number”. They’ve already IDed you at that point.

ZFS doesn’t have fsck because it already does the equivalent during import, reads and scrubs. Since it’s CoW and transaction based, it can rollback to a good state after power loss. So not only does it automatically check and fix things, it’s less likely to have a problem from power loss in the first place. I’ve used it on a home NAS for 10 years, survived many power outages without a UPS. Of course things can go terribly wrong and you end up with an unrecoverable dataset, and a UPS isn’t a bad idea for any computer if you want reliability.

Totally agree about mainline kernel inclusion, just makes everything easier and ZFS will always be a weird add-on in Linux.

The only problem I run into is sites that use Bluetooth or USB APIs to talk to a local device. Both Firefox and Safari don’t implement them due to security concerns.