On the software front, our fastest way to independence is a state-funded software org to fork Android and begin development and maintenance full-time. Whether one goes with non-Android or Android OS, it always comes down to funding development. Starting with Android would likely be significantly cheaper since a lot of work has already been done. And if you fund its continued development away from Google, then Google isn’t a factor anymore. Make an independent app store, Play Services replacement, etc. As I said in another thread, the social infrastructure (people, labour) is more important than the exact technology used. If we have that, we can make a usable phone out of Android or Sailfish, or anything else. It’s a matter of doing the work.
Having independent software with PRC-hardware isn’t a bad compromise. Especially in the near term.
You are likely correct that forking Android would be a better (cheaper and more efficient) option. But I can’t get rid of the feeling that it’s best to do a clean break with American oligarchy and make design choices that reflect regional priorities.
I understand that feeling. If it’s strong enough to drive to using a different base I wouldn’t care much even if it’s more work. The staffing and funding is the real difficult part.
From technical perspective, other than perhaps the software license choice, there’s nothing in AOSP that I’m aware of (not the closed source parts) that’s driven by the oligarchy. I’ve been involved with AOSP at the OEM level for some ten years, some in the early 2010s and then since 2020. AOSP has been fairly well isolated from non-technical decisionmaking at Google, in part due to how many third parties heavily depend on it, and in part because of how pluggable the APIs are. The plugability allowed all anti-features so far to go into installable components that don’t need to be a part of the OS. I think this bullshit with the app “sideloading” changes is the first major change that has no technical basis whatsoever that I’m aware of and requires AOSP surgery to accomodate. There may be more to come from here on out.
I guess you could chalk up the lack of open source app development as part of the oligatchic shitfuckery. I guess it is, but the base apps really are separate from the OS and they’re a pretty small effort compared to the rest of the OS and frameworks.
Anyway. I’ll get this next Jolla phone to try out. Sailfish is an evolution of MeeGo which was the most promising Android alternative in the early 2010s. 😁
On the software front, our fastest way to independence is a state-funded software org to fork Android and begin development and maintenance full-time. Whether one goes with non-Android or Android OS, it always comes down to funding development. Starting with Android would likely be significantly cheaper since a lot of work has already been done. And if you fund its continued development away from Google, then Google isn’t a factor anymore. Make an independent app store, Play Services replacement, etc. As I said in another thread, the social infrastructure (people, labour) is more important than the exact technology used. If we have that, we can make a usable phone out of Android or Sailfish, or anything else. It’s a matter of doing the work.
Having independent software with PRC-hardware isn’t a bad compromise. Especially in the near term.
You are likely correct that forking Android would be a better (cheaper and more efficient) option. But I can’t get rid of the feeling that it’s best to do a clean break with American oligarchy and make design choices that reflect regional priorities.
I understand that feeling. If it’s strong enough to drive to using a different base I wouldn’t care much even if it’s more work. The staffing and funding is the real difficult part.
From technical perspective, other than perhaps the software license choice, there’s nothing in AOSP that I’m aware of (not the closed source parts) that’s driven by the oligarchy. I’ve been involved with AOSP at the OEM level for some ten years, some in the early 2010s and then since 2020. AOSP has been fairly well isolated from non-technical decisionmaking at Google, in part due to how many third parties heavily depend on it, and in part because of how pluggable the APIs are. The plugability allowed all anti-features so far to go into installable components that don’t need to be a part of the OS. I think this bullshit with the app “sideloading” changes is the first major change that has no technical basis whatsoever that I’m aware of and requires AOSP surgery to accomodate. There may be more to come from here on out.
I guess you could chalk up the lack of open source app development as part of the oligatchic shitfuckery. I guess it is, but the base apps really are separate from the OS and they’re a pretty small effort compared to the rest of the OS and frameworks.
Anyway. I’ll get this next Jolla phone to try out. Sailfish is an evolution of MeeGo which was the most promising Android alternative in the early 2010s. 😁