Obviously we all want to avoid enshittified (aggressively monetized) software or at least get our money’s worth. I’m looking at self-hosting software right now and one I’m looking has a pricing page but only for cloud (no other paywalled features) and is open source. I tried looking up future plans and didn’t find much, so it doesn’t seem like it will enshittify. (not related) I had thought about switching to Omnivore for a long time but then they merged with ElevenLabs and the rest is history.
Green flags:
- copyleft license (GPL or better AGPL) + they accept contributions without contributor license agreement
- code written by many people who personally own the copyright
- active community
Yellow flags:
- permissive license
- business model which can’t be really be sustainable with a shit-free product
Red flags:
- VC funding (implies enshittification in future because of profit maximization)
- proprietary license
- project does not take contribution from the outside or asks to transfer copyright or sign some document (CLA)
I like to see companies design their software such that their main financial incentives are tied to the quality of their product. This usually involves being open source; if someone can fork it, your paywalled version better have extra features that open source people can’t make easily. I also like to see them trying to avoid vendor lockin; if it’s easy for you to switch, then they need to actively work on not letting that happen.
For example, Bluesky. They have an open protocol and (I think) you can easily transfer data between instances. If they start fucking people around, you can just jump to another ATProto app.
For Kagi, the only thing you’re paying for is search… So if they fuck that up, you can just crawl back to DuckDuckGo.
Obsidian is an interesting case. It’s not open source, but the files it works on are just markdown. If they go totally wild, I can just easily switch to VSCodium to edit my files.
For example, Bluesky. They have an open protocol and (I think) you can easily transfer data between instances. If they start fucking people around, you can just jump to another ATProto app.
I’ve never touched bluesky but everyone on Lemmy seems to be constantly saying that there are no other instances
Personally, I’m at the point where I try to only use community-developed software. I’ve seen it too often that even projects which are nominally open-source start becoming cunts…
Agreed. The downside of community developed software is it can very easily die. All too often almost all of the work is done by one or a few very active people. When they stop working on the project it’s a matter of luck if someone is willing to take it on. I’ve lost more than a few good tools that way.
My basic check is: Are there investors / vc people involved? If so, then it will inevitably enshittify. If not, then requires further investigation. OSI-approved open source is a big plus
Even when choosing what seems like good software, I think it’s important to consider switching costs. How easily can you move to another solution, say the second pick, if things go south?
Two very good points here. The second is the one I’ve been thinking about recently. It’s about considering what format your data is kept in and if you can usably get that out and implement it somewhere else without too much work.
Just use open source software?
Just because it’s open source and anyone could theoretically fork it doesn’t mean it can’t be enshitified.
It absolutely does… Can you elaborate on a situation in which FOSS gets enshittified?
Android, Chromium.
The problem is that:
- Google puts in more development power than anyone else. Any forks we’ve seen so far are only really soft forks, as in they only apply a few patches on top of what Google puts out, rather than taking the project in a new direction, because you’d be behind pretty quickly.
- These projects establish platforms that have shitty decisions baked in. For example, the Android dev tooling has Google ads/tracking as one of the built-in UI components, which is why even if you patch the OS, the apps will still be shitty. To actually change this stuff, you’d need a majority of users to switch to your fork and stay there for a few years.
- Partially, it’s only financially viable for Google to develop these projects, because they have those Android ads or benefit from a web with less tracking protection. This makes it extremely unlikely for any other organization to be able to splurge a similar amount of money, which brings us back to a fork just being unlikely.
And so long as a fork is unlikely, Google can do shitfuckery quite similar to proprietary projects.
Small teams are unable to take web browsers far in another direction as browsers have recklessly grown to one of the largest and most complicated software. Browsers do not follow the “do one thing well” philosophy, to the extreme.
Most functional parts of a browser (text reader, video player) are thankfully resistant to enshitification. That is if they are free (libre), permitting a fork.
My two examples are of OS SaaS that got their plug pulled before they got to that stage. See skiff.com and omnivore.
Ubuntu?
Red Hat and Ubuntu are two that leap to mind.
What’s wrong with Ubuntu and RH? Is it because of the snaps / source code debacle? Both of those had solid business cases to them and while I dislike the outcome, I do understand why they made that choice and most importantly - I still approximate what each company does for FOSS.
I don’t think you can. But if it’s open source and popular, there might be a chance it will have a maintained fork should that happen.
Freemium feature creep might be a sign things are changing for the worst, as in, if more and more features are being added to the premium plan and the free version is stagnating; to the point the target public of the premium version is creeping to average users instead of aiming at commercial or power users.
I’ve been focused, lately, on separation of concerns. Yeah, using FOSS tools is great, but I’m also asking myself how much losing a given tool will impact me if I start to rely on it.
This past weekend I finally broke away from ProtonMail. After what the CEO has been saying, and because of other annoyances like being unable to use anything but their clients, it was finally time to rip that bandaid off.
Unfortunately, I made the mistake of using a standard protonmail.com email address, so now I have to tell everyone to stop using that. Also, I was a heavy user of SimpleLogin for creating email aliases for basically every service I signed up for, and now I have to switch all of those.
I should have learned this lesson when I left Google, but this time I will be using my own domain. I also took this opportunity to leave Cloudflare entirely.
Now I have a domain for my email address and my website through porkbun, but can transfer that to another registrar if they start to suck.
I use desec.io for my DNS needs instead of the built-in porkbun DNS tools to make it easier to switch to a different registrar if I need to. They’re a non-profit, and it’s open source software that I could potentially selfhost in the future. This also replaced Cloudflare.
I use fastmail.com for the actual email service, which let’s me use the apps I like on my phone and PC to interact with email the way I want.
Fastmail also has a service like SimpleLogin, but instead I went with addy.io (also FOSS; also potentially selfhostable) with another custom domain at porkbun.
My website is a blog hosted by write.as, which is, again, built around FOSS and selfhostable software.
All of these pieces can be swapped out without affecting the others if need be, bringing switching costs to near-zero, and making it very customizable in the process.
If it’s not running on the cloud, I can always just stay on an old version. If it’s open source, that old version can be maintained and updated indefinitely.
I think it is not possible to avoid it in all cases, but the reputation and business practices of the controlling company are your best indicator. Any changes to a company’s culture may give signs if a piece of software may start to employ anti-consumer tactics.
Naturally, being closed source and in a dominant market position (i.e. a monopoly or near-monopoly) would make it easy for a company to start pulling these kinds of tactics. Sometimes even formerly reputable companies with open source software can try to do things like this after buyouts, changes in management, pressure from capital investors to increase profits, etc.
Generally, open source programs will be harder to monetize than closed source programs, as someone can fork the code and take out the disliked features. See Ungoogled chromium vs Google Chrome, VSCodium vs VSCode, Rocky Linux vs RHEL, etc.
