The consideration you should pay to other software should depend on your power and influence in the network.

If PixelFed was dominant in the fediverse, and other apps did feel the need for a dummy pic workaround, that would clearly be a problem. No client feels the need to do that because PixelFed is not dominant, but if it was, it would be fine to criticise them for not “playing nice” and helping the rest of the ecosystem.

I think there’s much more scope to criticise Mastodon for the workarounds other software have to use to be interoperable, than PixelFed, purely because of its power in the network.

We need different apps to experiment and work out what users want. It’s totally fine to experiment with different models and ways to view content. Only when you have a lot of influence over the ecosystem should you have extra responsibility.

This would kill bridges like slidge. They authenticate to WhatsApp using the web interface and that token lasts about two weeks before you have to relink it. A limit of six hours would make it unusable.

Yes Minister / Yes Prime Minister for me. Despite all the scheming the humour is so good-natured throughout.

Repology might kinda help for your use case. It lets you search for software that is packaged on many different “families” of distributions. You can also filter by category.

Admittedly it does kinda depends on your definition of popularity. But it’s good at answering these questions:

• Is this widely regarded as free software?
• Has it been around for a while?
• Is it useful enough to have been packaged in many places?

I run a prosody server and have a couple of users who run Monal, and notifications work reliably for us!

I made sure to follow the considerations for server admins and it’s been ok.

Regarding the push service: unless you deploy your own version of the app, it’s not possible to self-host your own push service. The flow looks like this:

XMPP server -> Monal pushserver -> Apple pushserver -> Device

Apple only allows the developer of the app to send notifications to their push server. They enforce this by giving the app developer a key specific to their app.

The linkage between XMPP server and Monal pushserver gets set up by Monal: when it connects to the XMPP server, it instructs it to send messages while it is offline to the Monal pushserver.

They will use CC BY-NC-SA 4.0. Which means it’s not open source, and no-one else can sell replacement cartridges, parts etc.

It might still be a good printer and enjoyed by some, but it really annoys me when companies mix these terms up, almost certainly deliberately.

My next laptop will probably be a Thinkpad T480 from Minifree. But I reckon it will be a while before this one breaks in an irreparable way.

CAD + ML is certainly difficult, maybe that needs a dedicated machine you only use for that? But that will increase costs overall. I’m also not sure how to find PC parts that I know won’t need dedicated firmware. So that part is definitely more tricky, I’m sorry I can’t be more help here :(

As for Matrix and XMPP, I started off with Matrix and found it pretty good for bridging lots of different networks together. But, over time, I came to prefer XMPP for a few reasons:

• Ultimately, I just don’t trust Element, and they do so much of the work. They complain that people are dependent on them and don’t give back, but they were the ones that created this dynamic in the first place. They are a single actor who own the dominant server, clients, and flagship instance, and can really push around the ecosystem in a way that works for them.
• XMPP is more community oriented, no one person can push through changes either at client, server, or server operator level. XMPP is based around extensions and there is an expectation that not every client or server implements every extension. That brings the con of inconsistent experiences, but at the same time, it is much more resilient over the long term (Matrix is now having to deal with the same fragmentation problems that XMPP started experiencing, and building solutions for, 20 years ago).
• XMPP’s network is less centralised, there’s not a mega-server like matrix.org with a lot of power. When matrix.org goes down (which happens semi-regularly), there is a big impact. If a single XMPP server goes down, it doesn’t cause nearly as big a problem. And, there aren’t those mega-instances with scaling problems, so the servers don’t go down as frequently anyway.
• XMPP evolves more slowly and gracefully IMO, as it is already more established (might be a con depending on your worldview). I run debian stable and an update across the Matrix network broke images on my Matrix client. That just doesn’t happen on XMPP, you can lag behind the leading edge for a couple of years and things don’t break even as the network evolves.
• I find XMPP easier to self-host - again subjective, but I could just install prosody via Debian’s archives, and once it was set up, I didn’t have to touch it. I update it with the rest of my server every 2 years, and I don’t fall behind the rest of the network or miss out on much in the meantime. Meanwhile, I have to pay much more attention to my matrix server, I get the software from upstream and not from my distribution, and there are more regular changes that I have to pay attention to.

As for advantages of Matrix:

• They have a flagship client that is available everywhere and has a decent and consistent UX. That name recognition makes it easier to get people to sign up. The XMPP community have done a lot of work to make signups work easily in a decentralised way, and projects like Snikket aim to solve that name recognition and consistency problem, but it is not 100% perfect yet.
• Bridge software to proprietary networks is more actively maintained in Matrix. There is work going on to improve this in XMPP, but I think many in the XMPP community moved focus from bridging to making the first-party experience better.

Many of the pros and cons are based on values (e.g. living on the leading edge vs using something more mature, preferring community based solutions vs commercial ones etc.), so I totally understand and support people who use Matrix instead. Ultimately, both ecosystems can cooperate, learn from each other and are millions of times better than the proprietary networks. That said, above is why I came to prefer XMPP.

I’ve had similar feelings before. You’re not the only one to struggle with this. You are pushing against the grain and doing something, aligned with your values, that 99% of people don’t know about.

What helped for me is separating what I can control from what I can’t. Everything on my device, that I personally choose to use, is under my control. So that is all free software, downloaded from system repositories, because I care about that. Meanwhile, everything I can’t control, I just gradually try to improve over time.

Here are the things I feel I can’t easily control:

I bought a laptop many years ago without free firmware for wifi, bluetooth, microcode etc. I like using devices as long as I can. Ok, no worries, lets just replace it with a Thinkpad next time.

My employer requires me to use Zoom, and some proprietary VNC client on my own device (on top of a load of proprietary software that I run on their devices). I don’t really have a choice here, unless I quit my job. So, I give in the short term, but do what I can to minimize the damage, running it in a dedicated VM. For the long term, I try and keep an eye on FOSS job boards and also network with people in the FOSS world (I’m quite bad at this, but trying to get better).

Likewise, some of my friends haven’t switched over to XMPP, which is my network of choice. Eventually, the people closest to me did, but many did not. So, I bridge those who haven’t into XMPP (via Matrix, for now, but looking to remove it eventually), and decided that I don’t want anyone “new” to contact me through the proprietary networks (I haven’t set up “enforcement” for this, an autoresponder probably, but this is the plan). The good news is that the proprietary networks always screw up eventually. When they do, your friends will get pissed off for their own reasons, and that is your chance to offer them the alternative. I never push, but let people know that I use XMPP. Some become genuinely interested, others you have to wait until they get screwed over by the proprietary networks.

Now bear in mind I am more interested in software freedom than security. So your priorities might be different. But the short story is: don’t beat yourself up over this. It’s a journey and you are pushing against the rest of society. What I do is just try and improve my setup, whatever that means to me, gradually over time.

I use podget, which is a 248 kB bash script. I really like it, and think it will meet your requirements:

• It’s designed to be called from cron
• It lets you sort your podcasts into categories
• It automatically organises the downloads into different directories based on these categories
• It’s been around since 2005 and is still maintained

From its description:

Podget is a simple podcast aggregator optimized for running as a scheduled background job (i.e. cron). It features support for downloading podcasts from RSS & ATOM XML feeds, for sorting the files into folders & categories, for importing URLs from iTunes PCAST files & OPML lists automatic M3U & ASX playlist creation, and automatic cleanup of old files.

It also features automatic UTF-16 conversion for podcasts hosted on MS Windows servers.

I have read so many posts like this, that try to explain why their company is a special case and why it could never happen to them, only to see the same thing happen again and again.

Tailscale are trying to insert themselves into the stack and become the go-to choice for this kind of networking. When their customers are dependent on it, of course they’ll start extracting rent and capturing as much as they can.

That’s their right, but it’s also a little condescending to pretend otherwise.

I for one would love to throw money at Mozilla, or any alternative, that has experienced developers behind it, doesn’t have conflicts of interest and acts on behalf of its users. This is why I donate to Servo, Ladybird and Dillo too (I know one of these is not like the others 😄).

I don’t think they’d reach their current levels of funding through donations, but it might be possible to get enough together to keep it on life support.

I know this wouldn’t be perfect, but surely better than losing it completely.

I host Synapse using this playbook. I can highly recommend it - the instructions are very clear and detailed and ongoing maintenance is straightforward too (just git pull and redeploy, and 5% of the time modify a deprecated variable).

As for how to delegate to a subdomain - that’s covered here. Basically - you set it up on matrix.example.eu and then have a “well known” file hosted at example.eu that tells other clients/servers where to look.

The only way to get people to switch from Adobe is to wait for Adobe to make the life unbearable for their own customers

Completely agree with this! The big opportunities to get mindshare will come completely out of the blue, and likely as a result of massive blunders on Adobe’s side.

We never know when the blunders will come, we just have to be ready and provide the next best user experience so that the free software is the “obvious” place to switch to.

As we saw from the twitter/reddit migrations, the fediverse did get a large amount of traction, but bluesky became the obvious alternative because its UI was basically the same.

And that’s fine - the fediverse is it’s own thing and many people (myself included) don’t want “adoption at all costs” - but I think it’s worth pointing out that it does hinder adoption in these big moments.

I have a lot of respect for free software projects that deliberately replicate the UI of an existing proprietary project. They make it so easy to recommend for people to switch when those moments come.

What I have seen is that once people get a taste of free software that really easily solves their problem, it makes the benefits “real” to them and they start to look for other alternatives on their own.

I agree with parts about entitlement. The expectation of support and treatment of open source software as if it was proprietary is a real problem.

But, the authour makes a similar mistake - they conflate open source software with source-available (proprietary) software. As an example, I strongly disagree with this part:

When software is open-source, it is open-source, not necessarily free and open-source (FOSS), and even if it is FOSS, it might still have a restrictive licence. The code being available in and of itself does not give you a right to take it, modify it, or redistribute it.

If you replace it with this version, I am happy:

When software is source-available, it is source-available, not necessarily open source or free and open-source (FOSS). The code being distributed under a source available license does not give you a right to take it, modify it, or redistribute it.

I think it’s really important that we keep a clear delineation between free/open source software on one side, and source-available (proprietary software) on the other.

A lot of companies are trying to co-opt and blur the meaning of the term so they can say “seeing the source was always the point, none of the other freedoms mattered”, in order to sell you proprietary licenses.

Open source gives you the right to take, modify and redistribute it. Source available does not. And that’s ok, just please don’t blur the terms together.

even if it is FOSS, it might still have a restrictive license

Likewise, this is definitionally untrue. The whole purpose of FOSS is to give you the four freedoms.

For services only I depend on, I have production-only. Since I can only inflict damage on myself, and can often work around problems.

For the XMPP server my friends and family also depend on, I have a dedicated nonprod VPS. My services are driven by ansible playbooks, so I’ll tweak the playbook with whatever change I want to make works in nonprod, before running the same playbook against prod.

Whenever there’s a new Debian Stable release, I’ll rebuild the servers completely, to try and prevent “drift” between the nonprod and prod versions (not that I change things often enough for this to become a big problem). This is also the big test of my backups, which so far haven’t been needed in a “real” emergency 🤞

Yep

I can highly recommend Mythic Beasts (UK).

There is no upsell or variable pricing and they make money by charging a flat rate on top of the cost from their supplier. See this blog post for more info

I would love for such a fund to invest very liberally in these companies, on the condition that anything it funds must be free and open source - public money, public code! The only way to take down these giant US companies is to work together, and the most effective way to work together is to release everything in the open in such a way that anyone can build on top of it.

If the money just gets funneled into these companies so they can build their own lock-in, the EU would be recreating the same dependency on a few small companies that happened in the US. It wouldn’t increase productivity in the long run, it would instead substitute dependency on a few US companies for a few EU companies.

But, if they invest in open source software, it could spur innovation not only in the companies that are directly funded, but also thousands of other companies throughout the EU that would now have common infrastructure that they can build on top of.

That’s good news, in my opinion. If they’re allowed to just completely disregard copyright when training, then I should be able to completely disregard any attempted copyright on the output too.

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.