@tasket @bart Good luck breaking secureboot, even for the sake of research.

Typically it's all signed and sometimes even completely encrypted, so unless you manage to find some bug in the bootROM (and good luck dumping that too), you'll have a hard time signing your custom firmware so it will accept it, and if encrypted (typically would be AES), you'll also have a hard time decrypting.

@noisytoot @7666 @ElDeadKennedy @eloy and I think they're getting rare anyway

@noisytoot @7666 @ElDeadKennedy @eloy I don't think D16 will be enough to compile Android in a timely manner.

@bart They already realised this. The FSF is no longer the one pushing FOSS forward anymore. Except for FSF hardcore fans, mostly everyone I saw talking about the LibrePhone think it will never materialize..

And that is true, really... They're planning to take a *recent* phone (likely MT/qcom) and reverse-engineer firmware .. something which is quite impossible because of things like secure boot.. hey, in postmarketOS it's also just impossible to use newer versions of that same proprietary firmware as long as they've not been approved by the manufacturer! Unless they manage to break secureboot (which is unlikely), of course.

All in all, this has too much red flags to be considered really serious. It seems they don't really have much experience in that area, and I'm not sure they want to collab with anyone that does.

Also, android.. Why android? I mean, assuming they're as purist as they claim to be, android is going to be a nightmare to compile on the FSF-approved ThinkPad X200 and such.. they'd be also relying on Google to publish Android source code, which they have recently been not doing all that frequently, and delaying security fixes to AOSP unless deemed "critical".

@ra1n @eloy The longterm solution is to run actual mainline Linux with a mainline userspace on our phones. That way we can have control over much more.

@ra1n @eloy Highly doubt. While Android is technically FOSS it is also predominantly developed by Google, so there's already a conflict of interest there.

And they won't stop there.

For example, the AOSP Dialer went unmaintained as most dev work went into Google's own proprietary Dialer app. There are many other examples of that conflict of interest, just need to find them.

@pocketvj :D

@eloy @ra1n tl;dr relying on Google for a "Freedom-respecting LibrePhone" is just weird and pointless

@ra1n @eloy Detailed about this here: https://berkeley.edu.pl/notice/AzF3URsZsaqBWyGujw

@ra1n @eloy Still not what I mean

@ra1n @eloy Please see above, this is not what I mean at all.

@ElDeadKennedy @7666 @eloy I don't mean X200 is bad, hey not even my laptop can compile Android fully in a timely manner.

But still good luck compiling Android on a RYF-certified X200. (Android is huge, unnecessarily huge, requires 64GB of RAM, 300 GB of disk space, an overpowered CPU, etc. No way X200 or even my laptop can compile it)

be me
look up images of budgies
expect funny cute animals
get disgusting AI-generated images
not even duckduckgo's AI filter works

:(

[22:21:19] <ellyqw> ~~we should make a comic about postmarketOS~~
[22:50:15] <lordkaczuha|m> that time i was reincarnated into another wolrd and was forced to mainline an arduino

#pmosleaks #postmarketos

@bart They already realised this. The FSF is no longer the one pushing FOSS forward anymore. Except for FSF hardcore fans, mostly everyone I saw talking about the LibrePhone think it will never materialize..

And that is true, really... They're planning to take a *recent* phone (likely MT/qcom) and reverse-engineer firmware .. something which is quite impossible because of things like secure boot.. hey, in postmarketOS it's also just impossible to use newer versions of that same proprietary firmware as long as they've not been approved by the manufacturer! Unless they manage to break secureboot (which is unlikely), of course.

All in all, this has too much red flags to be considered really serious. It seems they don't really have much experience in that area, and I'm not sure they want to collab with anyone that does.

Also, android.. Why android? I mean, assuming they're as purist as they claim to be, android is going to be a nightmare to compile on the FSF-approved ThinkPad X200 and such.. they'd be also relying on Google to publish Android source code, which they have recently been not doing all that frequently, and delaying security fixes to AOSP unless deemed "critical".

https://www.fsf.org/news/librephone-project

#FSF announces the #LibrePhone project, and, shockingly, it's a joke. While the intention to reverse engineer proprietary firmware is applaudable, going with Android for this and thus interfacing with the downstream kernel is a waste of time.

What good is software freedom when you're still relying on the goodwill and development of a big tech company.

#Android is dead in the water and it's time people caring about software freedom and privacy realize this.

@eloy Android is already dead in the water yes.

Even if you manage to deblob it you're still relying on Google for "freedom"... and that dependency is just getting worse as we speak.

Also good luck compiling Android on a RYF-certified ThinkPad X200

@eloy Android is already dead in the water yes.

Even if you manage to deblob it you're still relying on Google for "freedom"... and that dependency is just getting worse as we speak.

Also good luck compiling Android on a RYF-certified ThinkPad X200

My human says I'm very pretty. #CatsOfMastodon #Cats

Getting ready to install Mint.