There are also a few extra features, like "Advanced Privacy" which is mainly a domain based blocker, blocking connections to undesirable servers.

But mostly yes, LineageOS+microG.

Nhentai Operators Ordered to Expose Themselves in U.S. Copyright Lawsuit

Phrasing!

Damn, I went to read the linked post I Want to Love Linux, it Doesn't Love Me Back and it is, indeed, a banger.

I never understood leather car seats.

Can someone here explain to me the appeal of car seats that get extra cold in winter, extra hot in summer, and that will get all sticky against my sweaty leg if I sit down with shorts...

Can't even tell if serious or what.

The Inkscape tutorials are included in Inkscape's standard help menu and particularly cool... Because they're actually all Inkscape documents.

So when the tutorial can just tell you to click and rotate the rectangle just below and you can just do that.

That's pretty neat, and it's a pity that it just isn't possible or as easy in other kinds of programs.

I am writing right now from my degoogled Fairphone 4 running /e/OS.

I would buy again in a heartbeat.

It's definitely not the most bang for your bucks. But it's good enough for any use, it already outlived my last 3 phones, and it shows no sign of giving up (even when I was using the Google infested OS a few months back).

I'd recommend it.

FUTO Keyboard is hands down the best option.

If you have philosophical objections to the FUTO license, then your options are Heliboard and Florisboard. Heliboard is currently better, but Florisboard has promise.

I think you're missing the point. If this is confirmed as a policy change, it's not GrapheneOS that's dead... It's the Pixel as a mod-friendly device. And of course GrapheneOS runs only on that.

So the first thing you need to ask yourself is what's the next best device. I have a Fairphone, I like it, they are extremely supportive of the community (so far as to help porting PostmarketOS on 10 years old phones). Then you decide which Android ROM is the best. CalyxOS for instance sounds pretty good.

Using a Fairphone does include a few compromises in terms of security compared to a Pixel. How important that is to you is something you'll have to decide.

For me it's pretty fine. If, like almost everyone around here, you are a human rights activist in Iran. Then maybe you should just keep running GrapheneOS on you Pixel with Android 15 for a few more years.

Hopefully within a couple years we sort this mess out, and a new reference device emerges with a hardware security features that are not too much of a step down from the Pixels.

Cowabunga!

Also, they very intentionally decided to block use of their app on custom ROMs, cutting out all Graphene/Calyx/e/OS users.

So... not great.

I think that's language options, not geographic range.

He says he lives in Graz, in Austria (where people speak German and there are no kangaroos BTW).

The other 40 had to disagree with the majority out of a knee jerk reflex.

It was always burning since world's been turning!

Fr*nch.

Barry we're not on 2we4u

As others said, it's pretty stock android so... Bad. But you can buy it from Murena pre-flashed with e/os and then have a stock phone with a locked bootloader running a decently private OS. The bootloader is unlockable if you so wish.

Why? It's pretty clear that Google is mostly done with users having choices, particularly indovidual users, and all the more so on Google-branded hardware.

Manifest V3, Play Integrity, the attempt of introducing Web Integrity. How many more examples do you need to see?

This seems like a perfectly logical decision in that direction.

Does really no one get a song reference around here?

They are all either visa or MasterCard, which end up taking a cut. On top of that there is the whole massive problem of these two companies being gatekeepers and deciding what can or can't be traded in the world, whether it is legal or not.

https://www.theguardian.com/world/2025/jul/29/mastercard-visa-backlash-adult-games-removed-online-stores-steam-itchio-ntwnfb

I keep hitting my face on the fact that DKMS modules somehow don't depend on the kernel headers and these have to be installed manually. This happened to me both in Arch and in Debian.

Why does everyone seem to think that this makes sense?