Honest to God, I thought a "Librephone" was something that already existed. I think I was thinking of the PinePhone or smth.

For Fuck Sake its Free Software Foundation.

Yes, though the future of GrapheneOS on Pixels after 10 is currently in question

The issue is that for the FSF, what they call "software freedom" is their number one goal. So what's likely to happen is that they create some kind of "deblobbed" firmware that breaks many features and security of the device, which Graphene OS will refuse to use.

I hope this project will be useful but am worried that they'll just make a shittier version of someone else's work like they did with e.g. Libreboot.

`+ e-ink variant o.o if possible?

Genuinely curious, what on earth do you need a stylus for? I've never really understood the use case

What should be the highest priority in terms of being able to use a fully FOSS phone? I feel we already have FOSS alternatives for most things that make the phone usable.

Perhaps free hardware might be top, but the S in FSF is Software and being able to avoid non-free software would be close 2nd, imho.

I've worked with Qualcomm SoCs a long time ago and, from my experience, the binary blobs ARE the biggest hurdle to the true Foss phone. Google is the most to blame, IMO, but also the rest of traditional OEMS of SoCs. They basically found the way to circumvent the OSS nature of Linux, which is why even though android is based on linux, the actual product and ecosystem looks nothing like regular Linux. What Google allowed with Android architecture, particularly with their HAL subsystem is force a layer in between native Linux device interface and Android system, so OEMs use that to implement whatever proprietary peripheral (device, sensor, etc) purely in userspace, rather that just as a kernel module. The kernel module is then just a userspace/kernelspace adapter, and everything is handled in the user space. This then means you dont have to have an open source driver, as it is not a part of kernel, and you just lock your driver into a binary blob. And in case of Qualcomm and I assume other oems, everything is just a binary blob. All sensors, microphone, GPS, modem, EVERYTHING. Yes, you can boot a basic Linux kernel, but no other functionality will work. If you had access to the blob source, you'd be able to fix, update and use a newer kernel versions eventually. HAL is technically not the cause of the problem, but it's certainly an inspiration and almost a blueprint for how to lock down your hardware.

I expect it's a combination of all the above in some sense. They state they want to build on LineageOS (an Android variant) and replace its binary blobs, I expect the result would be a new custom ROM targeting specific compatible hardware with the goal of ultimately supporting usable phones working on fully Free Software.

What it's not is the creation of a libre hardware phone. I don't think they are working on hardware, at least not anytime soon. Also if by "Linux phones" you mean non-Android based, that's not necessarily a requirement (given that they mention LineageOS), but I expect regardless the kernel will be Linux without the blobs and it's entirely possible that they add support for installing their firmware on those "Linux phones".

I do kinda wish they’d focus on stuff that has a way bigger user impact 😅

The thing is that technically we already have fully usable FOSS software at that user level. Using for example LineageOS with F-droid as the only app store already gets you there. Whereas, ensuring your phone is not spying you or having some malicious functionality on the hardware/driver level is something that currently is simply not possible.

The FSF has always been doing the thankless job of championing for the things that are harder and less rewarding to do, but that will advance software freedom most for those who do seek it. Even when that thing is not necessarily the most popular/mainstream. I feel this has more of an impact in software freedom than, say, if they were to reinvent the wheel just to have their brand attached to it, and/or provide a slightly different UI to do the same thing other FOSS software already does.

HURD is not in development by FSF. It's a side project by professor Samuel Thibault in his spare time.

Whaaat? Drop the OG free Android distribution that has already supported hundreds of phone models across decades for a Google locked hardware with unknown future support from a vendor just announcing locking down everything they can? What is your logic?

But on the positive side, someone is finally attacking the last obstacle to using our expensive hardware however we want to: device drivers. I'm hopeful.

This is way better than that promise, thanks for explaining

They probably get to a very good 80% and then never finish it, just like their kernel. 😫