slock

I went the /e/os way and quickly turned back. Not to dismiss the effort of the maintainers, but it really felt like a frontend on lineage os meant to sell alternative cloud services. I did not find convincing arguments over a bare lineage os and the pretty much forced /e/ cloud was a total turn off.

I went the "real" security / privacy way and switched to grapheneos. Very happy overall, already went thought with 2 major os updates, no issues whatsoever. Only issue would be if you want Google pay (won't work on graphene). You'd need a pixel phone if that's in your budget. The pixel phones are great at photos, but pretty "meh" otherwise

I've not used it for quite a bit, but look at Thunderbird (a mozilla project iirc), it might do what you want as far as email is concerned. However do note that Microsoft is really closing things down in outlook/office these days, they really don't like people using a "real" Linux (they want people to use windows with all their crap and start menu ads, and just have a small Linux VM they call the wsl )

Graphene user here ! The privacy and security gains are quite huge. Play services are more or less regular apps, with the sandbox offering limited access. Some of the "advanced" security offered by graphene triggered a few times for me, sometime highlighting something sketchy in some apps.

Also, you can disable the internet permission for apps, which can effectively block a lot of stuff (ex : you install a supposedly offline game, but it stills asks for the permission: denied).

If your main concern is not depending too much on Google, your options are limited, and very, very flawed depending on how far you whish to go (went far down this rabbit hole, came back). One less "extreme" way, using graphene, is to install play services and everything dependent on a separate user account, and clone app from this account to the one you will use. Since alternate accounts are sandboxed and not running when not logged in, when you use your phone from the main account, you will effectively be almost goggle free.

Almost, because the main remaining privacy hole is notifications. A lot of things goes through GMS in order to reach your phone without melting your battery

The massive influx of new ratings could also simply be linked to the fact that the game is included in this month's humble choice, adding a ton of new players

It does, don't remember the details but at one point I let a packet capture tool on my phone run for a few days and checked which apps phoned home. Gboard was one of them. You'd besurprisesd at the amount of network traffic for most apps between 2-4 am.

Just remove its network permissions, and it works fine (without the phoning home part) AFAIK other spell checkers / autocomplete aren't quite there yet

It is also a huge deal because since (at least in France) the government forced ISPs to log DNS queries, a lot of browsers (and latest android and iOSversion's) have now migrated to DNS over https or TLS DNS, which means that the only clear text DNS query they can intercept is the one to fetch your secure DNS service address. Now, having a trusted CA installed in browsers means that they can also spoof the identity of this secure name service, and regain a bit of control.

They invested a lot in surveillance technology (for both good and bad reasons), and https, DNS and encrypted messaging / phone calls means this was all for nothing.

And yes, by being authorized as a trusted CA, you can effectively spoof pretty much anything by setting a proxy. Some tools even leverage this for app analysis. Look up mitmproxy for example, or squid. A lot of companies already do this to inspect inbound / outbound traffic.

I've seen this news published at a few different places, and IIRC they plan to use already existing exploits. You can read a bunch about what could potentially be used on the grapheneos website, specifically on how the modem and cellular network stack is very highly privileged on android at least, and it is very likely that most cellphones are vulnerable to some kind of code injection via a stingray, for example.

That's pretty much what DRM does, keeping us out of the inner working of stuff

That's pretty much what DRM does, keeping us out of the inner working of stuff