ambitiousslab

I'd prefer having both analogue and digital options for things, but I'm fine with requiring technology, as long as open standards are used throughout. That is the only way to ensure equal and non-discriminatory access.

You should never have to use any particular piece of software, or be forced to sign a terms of service, to go about your daily life. Requiring an app for everything only entrenches iOS and Android, and most apps really don't cater well for people with disabilities or other requirements.

Meanwhile, open standards allow a variety of software to be built that can cater for everyone's needs.

I've used Mobian stable and pmOS stable on both the Librem 5 and PinePhone Pro.

I also can't give in an-depth comparison, but apart from the obvious (differences in available packages, versions and OpenRC vs systemd), I found them basically identical. Both had difficulty keeping the modem connected for more than an hour at a time, but otherwise did everything I expected (wifi, text messages, mobile networks, adaptaive apps, cameras, music/podcasts, etc).

For now, I'm sticking with pmOS, as, for the current stable version, Mobian doesn't offer prebuilt Librem 5 images with full disk encryption support (I can't remember why - this is specific to the device, and I'm hoping it will be fixed in the next release).

This affects me a lot day to day. I have a phone, but it runs postmarketOS, not iOS or Android. It really shows me the importance of open standards. I feel that every business should be required to support open standards for each of the services they offer.

For me, buying train tickets used to be ok, but is getting harder now. Some train operators are really pushing you to use their app now, and getting rid of the option to download a PDF. It really frustrates me: it's not like it costs them more to offer PDF download - if anything, it's much cheaper to offer that functionality than to build and maintain an app for iOS and Android.

Back when I had an Android phone, I used Monzo, and it was so easy to send money to friends, set up standing orders etc. I wish they offered a proper web interface. Now, I use Natwest's online banking, and it's a real pain - I use the card reader to authenticate, then the website logs me out seemingly every 2 mins of inactivity. Some features, like pre-notifying that you'll be travelling abroad, are only available on the app. I only see this trend continuing.

The concert tickets example in the article is insane to me. I can't think of a use case that is better suited for PDFs, and that's what we've been doing for the last 10+ years without any issues. It really is user hostile and excludes people on the edges of society who don't fit, for whatever reason, with what the 80-90% do.

Yes, me too! But, only if I have the autonomy to improve things where I can. Otherwise, I just find it demotivating

I agree, it's a great UI in terms of speed and no JS, but it's not super intuitive and not helped by the way it's been split into modules.

Basically, each subdomain (git.sr.ht, todo.sr.ht etc) doesn't link to the others - the only one that links everywhere is the root "sr.ht". You can think of sr.ht as a "hub" that links to the others. So - to take an example:

• You can open "tickets" (todo.sr.ht) from https://sr.ht/~delthas/senpai/
• But - if you click on "source" (git.sr.ht), the references to the other pages anymore (including back to the hub)

So, in your case, if you replace git.sr.ht with just sr.ht in the URL, it should take you back to the "hub" for that project. Then, if the tickets feature is enabled, you should see a link to "tickets" there.

I think (and hope!) it would likely only get applied to the biggest services, and would be enforced by removal from the app stores.

Then, the logical next step for the government when this doesn't work would be to allow this requirement at the OS level.

To answer seriously: unfortunately, the UK is one step ahead with the Online Safety Act. They've already given Ofcom the power to enforce client-side scanning. Ofcom themselves are deciding whether they want to use this power yet and this should happen sometime next year.

The frontends provide other benefits on top of just privacy - e.g. invidious lets you watch youtube videos without javascript, download videos directly on some instances, etc.

Just as a warning, this is licensed under the AGPL, with a CLA that requires copyright assignment. So, they could pull the rug at any time:

2.3 Outbound License. Based on the grant of rights in Sections 2.1 and 2.2, if We include Your Contribution in a Material, We may license the Contribution under any license, including copyleft, permissive, commercial, or proprietary licenses.

On iPhone, I recommend Monal.

Monal comes close.

nlnet is the main one that comes to mind.