I donate to Ladybird and Servo, and I hope they succeed. We need serious competition and a check on Mozilla (not to mention Chrome and Safari).

That said, I’m sad that neither Ladybird or Servo are licensed under strong copyleft licenses. We need user-oriented browsers now more than ever, and strong copyleft enables that. I worry that, even if these engines are successful, they will be co-opted by proprietary browsers and eventually superseded by them.

This happened before - both Chrome and Safari ultimately derive from KHTML, Konqueror’s browser engine. If KHTML had been licnesed under the GPL instead of the LGPL, Chrome and Safari (and not just their engines) may have been free software today. Or, at the very least, it would have been much more difficult for Apple and Google to get started.

That said, I wish Ladybird the best. There donation = no influence policy is excellent, and I really, really hope they can stick to it in the long term.

I made a comment about this on another thread, see this comment.

You can do this using JMP Chat, which bridges phone numbers to XMPP. Unfortunately, it’s USA and Canada only, for now.

Alternatively, you can use a “SIP Trunk Provider”. For instance, in the UK, Andrews and Arnold offers this service. You can then connect any compatible SIP client (e.g. Gnome Calls).

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.

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.

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.

nlnet is the main one that comes to mind.

How much money do you donate?

I am very privileged to have some money left over after fulfilling essential needs. So, I set a fixed amount a while ago, and then whenever I am able to make a saving (e.g. switching to a cheaper phone plan) or get a pay rise (if it ever comes), I’ll put some of the gains into donations.

When do you donate?

I remember reading somewhere that many organisations prefer regular donations to one-off donations, even if the regular amount is smaller, since it helps them plan better. So I always give regular donations, even if the amount is smaller to compensate.

I have everything set up as automatic donations in liberapay and OpenCollective. So, it’s pretty seamless!

If anyone ever wants to gift me anything, I’ll ask for them to consider a donation to a project instead.

Do you have a minimum donation amount?

I try to avoid payments under £5. Below that point, way too much of the money goes to fees. For some projects where I donate a small amount, I donate yearly instead of monthly instead.

How do you decide what projects to support? Do you forego donations if you’ve contributed in other ways?

I don’t donate to every project I benefit from, but I care a lot about XMPP and Linux on Mobile, so I donate mainly to projects in these areas. I’ve also contributed code to some of these projects, but I keep donating as I want to support the ongoing maintenance as well as just individual features.

Do you donate to all equally or do you have some sort of ranking? Is it by amount of use, subjective preference, something else?

I care about XMPP as a whole succeeding, so I donate to many projects I don’t even use myself. I wanted to donate to clients and servers for each major platform, so I split the clients like this:

• iOS clients: 1 project
• Android clients: 1 project
• Linux clients: 4 projects
• Server software: 1 project

Then, I donated an equal amount to each platform (so, for example all the Linux clients combined would get the same as the single Android client).

However, since I was donating so little to each Linux client, I decided to gradually increase the amount I donate to those over time.

I’ve also recently started donating to libraries / ancillary projects in the same space. But I don’t have much money left to play with for them, so the amount is smaller :(

Linux on Mobile is simpler as I only donate to two projects, so I just donate equally to both.

So, long story short, it started with some kind of structure, but has become more subjective since then :)

What platforms do you prefer using? Liberapay, Opencollective, Patreon, ko-fi, Paypal, Monero, actual post?

I really like liberapay, especially as it mostly works without Javascript. But Opencollective is pretty nice too. If the developer themselves gives a preference, I’ll normally use that platform.

One thing I’m interesting in knowing is - do people generally prefer donating to fewer projects, but with bigger amounts, or vice versa? One criticism of my approach is that, because I am spread quite thin, I risk not really helping any project that much, whereas if I focused on one or two projects, at least those could benefit a bit more.

Any new open source software is always a net positive.

But, there are a few small caveats to the way they’ve done it (depending on how cynical/cautious you are):

• Because Proton are not accepting contributions, they own all the copyright, so can make the code closed source again if they want to (that wouldn’t affect the already released versions, but future versions)
• They could likely take down any derivative on iOS, since Apple will always take instruction from the copyright holder, for GPL’d code
• Since the builds are not reproducible, there’s no guarantee that the binaries they distribute are built from the source code

They have also funded a lot of improvements to XMPP clients and servers.

I’ve had good fortune converting some family and friends to use XMPP.

People always mention fragmentation, and while there is some truth to it, it can be massively minimised by choosing blessed clients and servers for them to use.

In my case, I run my own server, and thoroughly test the clients (especially the onboarding flow) that I expect them to use, so that any question they have, I can help them out with quickly. Since we’re all on identically configured servers, it minimises one whole class of incompatibilities.

There is still unfortunately a bit of a usability gap compared to Signal - particularly on the iOS clients. But they have come a long way and are consistently improving.