FrostyPolicy

Valve releasing Proton.

Whatsapp uses the same protocol as signal so MITM is unlikely however there's no way to know what happens before or after the messages are encrypted/decrypted and sent. They can do that scanning at that stage.

That is different than Signal which (unless they changed something with the profiles thing) was always P2P E2EE. You’re sending encrypted messages directly to the other persons phone, not to a server.

Sender cannot know where the recipient is and using P2P would be resource consuming on all client devices (i.e. everyone who uses Signal) so I guess the messages are routed thru Signal's servers though messages are encrypted on device with keys that only the messaging parties know (couldn't find an official diagram for this to confirm).

In a country with good consumer rights, this would be a valid reason to return it and get a replacement or refund: It’s no longer offering functionality that was advertised and that you paid for as part of the purchase price.

In the EU this would probably be a no-brainer.

Wonder how they'd manage that as they both are E2EE.

You won’t get rid of google tracking you on Youtube or Gmail,

For gmail that's true (one should use something else anyhow). For youtube you can use an alternative frontend like NewPipe to avoid tracking.

If you care about privacy you should use a trustworthy paid email. They even aren't that expensive. You can get them as low as 1 € / month.

You can basically disable most Google tracking though a good DNS that blocks that traffic.

So only most but not all. Therefore it's not private if there's any tracking. Thus a de-googled version is the only option.

Have you checked the source code that they actually respect private dns setting for their tracking? Or otherwise verified that no traffic goes to google tracking servers?

If there's tracking it's not private.

Here's a good list: https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md

It can't be removed. That info comes straight from the hardware itself (UEFI and individual devices).

This didn’t seem to occur in Windows, but I’m pretty sure the copy process was also slower so guessing it’s some sort of buffer or heat quirk that 'nix didn’t account for in the more generic driver

If the device says it's a generic storage device (to the system that is) but actually isn't (based on your description) then it's 100% devices fault and not a Linux fault.

This command won't show the real values when using btrfs. You need to use sudo btrfs filesystem usage <mount point>.