Man, I really hope they're the manufacturing partner GrapheneOS is talking about, or they at least include Verizon support on future models. T-mobile just doesn't do it for me out in the middle of the forest.
I know, but it's looking more and more like there won't be an alternative for long. I'd rather have a consortium of interests united in moving a fork forward as the core for all of their own OS's.
I really wish Sony would come back to the US market. I'm tempted to get an older Xperia device to run Sailfish, but it would be like 4-5 years old, and it's time on the Verizon network would be limited.
Honestly, I don't know if having play services running in a profile that can be deleted would pass that standard for certification. Probably not, I guess.
As for being a fork, I mean the larger community of Graphene, Lineage, Calyx if it continues to exist, and probably a couple Chinese manufacturers who rely on AOSP to manage a fork that is collaboratively developed going forward, that no longer relies on Google's maintenance of the project.
Last I checked, they'll pre-install any number of distros. I just... I don't know what I'd use it for that justified a separate device from a laptop. Maybe once I get home assistant setup in my new place, but even then... what I'm really wanting is a Linux phone that I can use on Verizon's network. But even there, I'm tending towards moving to my cell phone sitting on the charger 95% of the time, and using kdeconnect.
That seems to be their mid-term strategy, release their own certified device. That should have some interesting implications on safetynet attestation, too.
I still think we need a fork of AOSP, before the community atrophies any further.
On the one hand, a totally unified party is clearly a problem. I don't particularly want the Democrats to be united on everything, we can see from the Republicans that is a recipe for authoritarianism.
On the other hand, it would be nice if they could fucking unite against authoritarianism.
Is it offering SMS? I ported to jmp.chat recently, using their XMPP gateway for voice and SMS. They offer a VOIP option, but don't support SMS.
I like being able to SMS, and I guess call, from my laptop. But there aren't any Linux XMPP clients that I'm particularly happy with, so I'm just using Cheogram in Waydroid. It's not exactly optimal.
Nothing is perfect here, but I think federation would be best. The concern is the same one that caused Signal to drop SMS support (to my knowledge), that people might improperly trust the services that their anonymous service are federated to. Especially when you're federated to a chat service that is run by a company that also handles the synchronization of it's users contacts with their names, phone numbers, and email addresses.
But still, in a sane world, federation of services should be the goal.
I don't think it's an indictment of the concept, but rather a failure to realize it. I think there are two big improvements to be made, that would solve the author's issues:
Seamless user switching, with user recognition by fingerprint and voice
Make the dock function like a nest mini when the tablet is not present
Man, I really hope they're the manufacturing partner GrapheneOS is talking about, or they at least include Verizon support on future models. T-mobile just doesn't do it for me out in the middle of the forest.
I know, but it's looking more and more like there won't be an alternative for long. I'd rather have a consortium of interests united in moving a fork forward as the core for all of their own OS's.
I really wish Sony would come back to the US market. I'm tempted to get an older Xperia device to run Sailfish, but it would be like 4-5 years old, and it's time on the Verizon network would be limited.
It's on the N350, and is going to be pretty limited, though well supported in mainline.
https://www.intel.com/content/www/us/en/products/sku/241638/intel-core-3-processor-n350-6m-cache-up-to-3-90-ghz/specifications.html
Honestly, I don't know if having play services running in a profile that can be deleted would pass that standard for certification. Probably not, I guess.
As for being a fork, I mean the larger community of Graphene, Lineage, Calyx if it continues to exist, and probably a couple Chinese manufacturers who rely on AOSP to manage a fork that is collaboratively developed going forward, that no longer relies on Google's maintenance of the project.
Last I checked, they'll pre-install any number of distros. I just... I don't know what I'd use it for that justified a separate device from a laptop. Maybe once I get home assistant setup in my new place, but even then... what I'm really wanting is a Linux phone that I can use on Verizon's network. But even there, I'm tending towards moving to my cell phone sitting on the charger 95% of the time, and using kdeconnect.
That seems to be their mid-term strategy, release their own certified device. That should have some interesting implications on safetynet attestation, too.
I still think we need a fork of AOSP, before the community atrophies any further.
I keep looking at the Starlite, it's recently upgraded to an N350. But every time I'm about to pull the trigger, I can't come up with enough use case.
On the one hand, a totally unified party is clearly a problem. I don't particularly want the Democrats to be united on everything, we can see from the Republicans that is a recipe for authoritarianism.
On the other hand, it would be nice if they could fucking unite against authoritarianism.
Is it offering SMS? I ported to jmp.chat recently, using their XMPP gateway for voice and SMS. They offer a VOIP option, but don't support SMS.
I like being able to SMS, and I guess call, from my laptop. But there aren't any Linux XMPP clients that I'm particularly happy with, so I'm just using Cheogram in Waydroid. It's not exactly optimal.
Nothing is perfect here, but I think federation would be best. The concern is the same one that caused Signal to drop SMS support (to my knowledge), that people might improperly trust the services that their anonymous service are federated to. Especially when you're federated to a chat service that is run by a company that also handles the synchronization of it's users contacts with their names, phone numbers, and email addresses.
But still, in a sane world, federation of services should be the goal.
I don't think it's an indictment of the concept, but rather a failure to realize it. I think there are two big improvements to be made, that would solve the author's issues: