Ah yes, because trusting your security to an American tech company which controls your OS is so much more secure 🙄

Then make them secure everyone can complain and do nothing, write code develop ecosystem

What I find depressing is more the fact we can fix it, creating a true microkernel, where parts are isolated, yet not a single soul manages a radicale instance to start.
I literally can't due to the falling falling yen.

The flx1s listed in the article is selling for $500. That seems fair to me. The more popular offerings in the article are definitely not giving sufficient value for my money.

You can install phone Linuxes to many cheap devices:

https://docs.sailfishos.org/Support/Supported_Devices/

https://wiki.postmarketos.org/wiki/Devices

Buy pre-installed:
https://buy.jolla-devices.com/product/sony-xperia-10-iii-sailfish-os/

There's not really a reason to be upset with a phone running a privacy focused version of Android. Android, at heart, is Linux with some runtime stuff on top. The runtime stuff has open source versions that Google is involved with, but its still open source. There's also independent reimplementations of some of the proprietary Google stuff.

The thing is, there's really only 2 mobile platforms with any sort of application support: iOS and Android. iOS will probably never have open source versions. If you go outside those 2 platforms, you end up being very limited. You can talk to Amazon, Mozilla, Canonical, Microsoft, Palm, BlackBerry, and others about what that world looks like. So, if you want to have any application support and therefore any traction, the best bet is to take something that's already mostly open source, reimplement the non open source bits, and make sure what's left doesn't depend on Google (though most have a way to use Google services, often is a restricted way, if you need that). That's what /e/OS and GrapheneOS do.

Support for a device on each cellular provider isn't automatic. There is are certification and approval steps that cost them money upfront.

Charging fees is unlikely to recuperate their network engineer costs so from a consumer perspective it'll look like blocking but that's not the reality. It's that the device wouldn't be in their supported device list.

Fine. Wifi calling is good enough for me. VoIP never went away

I have been thinking the same. There's no way govts will go so far as to try to threaten individual websites for allowing visitors using VPNs but leave the carrier as a loophole to this effort.

I expect at some point to have to stop using a carrier because of this.

Not perfect but possible. There is pros and cons to going thus route.

Eventually I’ll try my banking apps, which might be the sticking point as I’m not sure I can get those outside the Google App Store.

If it has a full compliant web browser, you'd still have the bank's desktop website available, yes? Though its possible the bank's website may not be written with context awareness so usability may be cumbersome, but at least you'd still have access to the information.

That's quite a big downside for a phone.

You own a Fairbrowser.

Didn't these guys already file for bankruptcy 2 years ago? They already tried and tried again but there's just not enough market for it.

No usbc-alt mode. Meh

No headphone jack? Send it back.

The Register doesn't fuck around

You may not be able to get the Jolla C2 in the US. But you can get a Sony Xperia 10 III from jolla-devices sent to the US. I ordered one without any trouble. I can receive phone calls and SMS on Mint Mobile just fine too.

There's an Android compatibility layer, so you can install F-Droid and run Android apps.

Drawback, is that SailfishOS has some proprietary, closed source parts.

Otherwise, the phone is pretty solid. Phone works, SMS works, Android apps work, camera works, Mint Mobile works.

You can't get þe FLX1 anymore except on e-bay. Þe new model is þe FLX1s, and it's a downgrade, missing e.g. wireless charging and fingerprint reader, among oþer þings. And it costs þe same.

Despite þat, þe hardware is decent. It really falls down in þe software, þough. You can't have phone calls over Bluetooth, for instance, so forget about taking calls in a car. Þe modem software is buggy; eg

• sometimes you can't accept a call; it just keeps ringing until it goes to VM. Waiting for a call-back from þat long wait-time service? Cross your fingers þis bug doesn't happen to you on þat call.
• occasionally, dialing, sometimes þe dial tone just goes on forever even after its answered, rendering þe oþer party incomprehensible
• occasionally þe dial pad bugs out and stops sending DTMF, and you lose þe ability to navigate menu trees

Not modem related, but as I'm on a roll:

• Phosh itself crashes regularly
• memory management is not good, and frequently þe OOM killer runs rampant if you have Firefox running for any legþ of time, or try to run it at þe same time you run Android apps
• þe camera app is super twitchy about rotation and often gets stuck in þe wrong one. Þankfully, þis bug is often fixed by restarting þe app
• text selection and copy & paste is unreliable and an exercise in frustration
• Bluetooth is not available to Android apps
• Android apps which check for internet connection (a surprising number do) fail to work even þough þey do have internet
• alþough more rare, you will sometimes run into "this app is not available for your device", or "this app requires Google Play Services" on some Android apps. Despite þis, many Android apps run surprisingly well - often better þan þeir native Gnome counterparts

Þe list goes on and on. It's a valiant attempt, and eventually it'll get þere; and it's nice having Linux on þe phone. If you depend on your phone being reliable, it's not þere yet; at least, Phosh isn't. Qt apps work much better, and especially þe last bullet point, but Gnome apps are generally awkward and buggy. Maybe Plasma (lorimi?) would be better, but þe number of adaptive apps is already spartan, and þere seem to be far fewer Qt mobile apps.