

For very different use cases (barefoot shoes)
- wildling
- many others I forgor 💀


For very different use cases (barefoot shoes)
Afaik SailfishOS is proprietary. The rest of the marketing was extremely vague and not trustworthy to me.
Also if the phone doesnt have a headphone jack I am gonna cry


What


DivestOS is dead. CalyxOS is paused. I specifically meant Android builds that have up-to-date build systems but support devices that are EOL from their creators.
They cannot sign firmware and thus not install it even if it was reverse engineered. And they might not patch an updated kernel to work, and ship an outdated kernel instead.


This is not about tracking but basic security patches. I feel we are talking past each other


Cool. Now research what that even means.
(It does not include firmware, baseband firmware i.e. anything running with airplane mode off, likely the kernel)


You mostly rely on vendor kernels, that is the point. The operating system would have updated it for you if it was actually still maintained.
Good operating systems will tell you that this OS is not secure anymore (if it ever was). But many that people use dont say anything while maybe even still shipping updates, so people think it is fine.


Yeah haha I tried finding one but no success.
I know they delayed the Android 14 upgrade and skipped directly to 15, even “bricking” some devices. Probably nothing very bad (though as they allow bootloader locking even on custom Android builds… it could really mean brick).


Very longterm, support ended over 1 year ago. That kernel is 7 years old…
Android is very conservative with kernel upgrades, but this is insane.


Can you check how old your kernel is?
uname -r


Fairphone absolutely is important and may have driven the long update span of phones. But note that because they were the first, they didnt use a secure smartphone SOC in their phone but an IOT one, lacking any secure element for example. Cracking that phone is not hard for people with the knowledge.
Also their firmware and software updates are often far behind upstream, which has obvious security implications.


That is a vast oversimplifications. Custom Android builds either rely on reverse engineered drivers, or vendor kernels, or mostly undocumented drivers and custom kernel patches.
Custom “ROMs” are often very insecure, as they use the outdated stock vendor kernel of the original OS, as it is so customized. Not always, but often.
Then you have firmware, which is responsible for a ton of tasks on Android phones, way more importantly than on a PC. There is an entire separate, proprietary chip in there, connecting to sensible and insecure networks like 2G and 3G (the modem/baseband).


Uhm your phone is EOL since a very long time. I hope you never turn off airplane mode
It does for me
https://github.com/futo-org/fcast
https://news.ycombinator.com/item?id=41376215
They will have hardware compatible with the protocol/software listed somewhere.
FUTO does some things


Yes but this ignores open source which is most of the time just good, and doesnt need to be forced to it through regulation
Xmpp or matrix are good Messaging protocols, and both are international projects.
What is the appeal? I dont get it
And yes I guess Joplin/Obsidian/Logseq
Depends on how you like the balance between open-source, control, self-hosting/independent sync and ease of usel/“just works”