I understand him though, GrapheneOS without the underlying security hardware is a huge security risk for the end user. It makes people think they get benefits from running a secure os while in fact, they are at the same level as running lineage.
Proprietary blobs are also present throughout regular linux distributions. And I hear and participate with the moans they generate but users understand that sometimes modems, wireless chips or GPUs (main culprits) have us stuck at the onset of using Linux at all. Debian had to reverse it’s procedure from a default free only to default mix and user has to specify if he doesn’t want proprietary firmware installed. Even graphene OS has to make do with proprietary firmware.
Jolla has sailfish OS as the official ROM and it has for quite a few years now (for all their past phones). It’s not marketed as a dev experimental.
I haven’t heard them say what format will be included in the torrent, say it’s 20 TB blocks of secured archival format. Then you would have to download that full volume ( at least, there are ways to force you to download the full 15 set of 20 TB archives) before decompressing it and see files as is, that would rendering streaming or casual downloading impossible under current tech.
And that’s ok.
Anna’s archive isn’t there to cater to today’s wants but to protect what might disappear tomorrow.
As Stallman said: " it’s free as in Free speech not as in Free beer".
Money in FOSS keeps projects going.
But as another said: in the case of LLM agents, monetisation is a way to get the automated skimming out of their lives. It eats resources, time, causes havoc on hosts…
Separate folders in the download one. One for each app. And a separate /home/sync folder with the same app separation folders to safekeep the backups of android apps and DCIM folder.
Not using it but I heard curve does it too over graphene OS. (And no, it’s not a bank nor FOSS) But if a tokenised wallet app is all that keeps you from Moving forward …)
It’s up to us, users of those FOSS apps, to collectively pour more money into the pockets of FOSS devs to make f-droid more important to their bottom line (and for a lot of FOSS apps that are also distributed on the play store, it won’t be hard to be a bigger financial input) so that when the requirement is pushed to their play store account, they feel free to decide to side with their hearts and say goodbye play store, knowing this community will keep them fed.
Time for many of us to get aquainted with the liberapay button on most app pages in f-droid.
Maybe it was a stray Android dev who moonshines in FOSS projects or their security team that is a fan of GOS’s secure implementation of Android (Yes, they are rightfully admired by many of the big guys for That) or : What part of their soul did Graphene sell to get that early access?
RMS warned of this a bit over 20 years ago. This is why you should get Free and Open source software and not Open Source Software. Preferably with a GPL licence which allows you to download, run, read the code, modify it and share it. Open source can mean you only have the right to read the code and signal to the dev code you’ve saw that could have been better or errors you saw.
They are correct. It only means more work for future devices, makes the initial port to a device slower. But then, once things have been figured out. It becomes just as fast and reliable as it was (unless what I said earlier: Google setting things in a very different way in a major update (for example, moving to Fushia, which has been abandoned)
I agree, but it’s more complicated than that: They have removed the device tree for pixel devices from AOSP and using the device tree of the basic virtual phone in android studio instead. That brings the pixel 10 family (as well as future android pixel devices) to the same level as many other phonemaker’s devices as far as making roms is concerned. So not all hardware will be documented, many drivers will need to be rebuilt. The pixel line up to the 9a is not affected because older device trees can be used (until Google wants to mod the way drivers load or add API’s).
It’s Thunderbird… Of course they release the code! How would it even exist without releasing the code?
BTW: K-9 is also Thunderbird.
Pixel 10 are set get quite powerful GPUs with raytracing etc
Google is starting to use DRM on all it’s videos so that only the official youtube clients on devices and big browser brands can play them. It also kills all the systems like invidious.
I mean the chips cores being 100% Designed by AI using Alphachip (which has been open sourced by Google) or other AI only chip designing tools instead of using off the shelf ARM or RISC cores.
I don’t know how they spent so much time with Samsung, especially since TSMC is accostumed to using alphachip for the dimensity line, the same AI chip designing tool Google uses for it’s NPU’s. Iwonder what it could mean for the future of chip design, is the ARM architecture about to be rendered irelevant by AI.
It’s not fdroid that doesn’t make it easy to insyall apps that are open source but not FOSS, it’s the licence of the non gpl open source softwarebthat usualy bans modifying, building and redistributing the code. It’s not foss, it’s just viewable source.
Because in the main repo of fdroid, the apps code is quickly eyed then packaged by the fdroid team from source (plus a quick virus scan. Google only does reputation check and use virus total (their android anti-virus and anti malware software), yes, the same virus total you can access as an app or webpage.
Motorola will only have 1 phone with grapheneOS on it and GrapheneOS will dev for that one device but they won’t dev for other Motorola devices. Do not expect to pick up any moto phones except that one device and flash grapheneOS on it.