Yes, ideally that's what should happen.

In practice, I've seen way too many times big corpo getting away with anticonsumer practices because their mainstream audience is willing to put up with it.

Specially when they introduce it slowly (say.. they start by allowing a reasonable but fixed number of keys ..then they lower the limit but start putting a small fee for each additional key.. then they lower the limit to 1, increase the fee, etc).. they'll test the waters and try to reach a level that enough of the mainstream would accept to maximize the money they make.

You can have an infinite number of tokens with a single YubiKey, but that's not the concern.

The issue is that a website can limit how many different passkeys you are allowed to register to a single account of their service.

So it does not matter if your device can provide infinite keys when the service only accepts one.

I think the concern is more about the freedom for the user to be able to decide what keys to use and how.

In particular, the author seems to want to share 1 account with multiple people, and enforcing "User-Present User-Verified Non-Copyable Hardware-Backed passkey" as the only accepted method for a service would allow for services to start restricting account sharing more effectively.

A lot of my favorite apps are there.

Material Files, Librera reader, KeepassDX, Syncthing, AntennaPod, Seal, Echo, and a bunch of open source games like Unciv, Xeonjia and Shattered Pixel Dungeon, or Idle Fantasy if you like idle games.

If you are into self hosting (I am) they have multiple Jellyfin clients, Immich client, etc.

There's also Lemmy clients.

And Termux if you are comfortable with tinkering in the terminal. I use it to run a privoxy and ssh server from my phone that I can connect to from my work computer. It helps me get past some firewalls.

I generally agree but it depends on the application and the computer purpose / input you will most use.

Like.. it doesn't make much sense to have a CLI/TUI for an image editor.. if you start using things like sixel you are essentially building a GUI that runs in a terminal, not a TUI. The same happens with videogames, video players and related entertainment applications.

But like I said, I do generally agree. I'd even argue that when possible, GUIs should just be frontends that ultimately just call the corresponding CLI programs with the appropriate parameters, avoiding duplication.

And even if they did somehow manage to get permission to switch the license, all previous versions would still be open in perpetuity so a fork would come easily. Immich source isn't only open, and not only GPL.. but AGPL-3.0 which is as copyleft as you can get.

So paying in order to prevent search engine competition is ok as long as you are rich enough that your payments become essential for those receiving them.

This is grounded in the assertion that a website’s HTML/CSS is a protected computer program that an ad blocker intervenes in the in-memory execution structures (DOM, CSSOM, rendering tree), this constituting unlawful reproduction and modification.

This is ridiculous... the in-memory structures are highly browser dependent, the browser is the one controlling how the DOM is represented in memory.. it would imply that opening the website AT ALL in a different version of the exact specific one they target or with a different set of specific features/settings would also be a violation, since the memory structure would likely be different too.

At that point, they might as well just ask for their website to not be visited at all.

Thunar is a much better alternative, in my opinion.

I think that's the point, he's saying he'd rather use USA-linked FOSS than non-USA proprietary software.

From what I gather, I don't think it's about any stance from Codeberg in general, it seems they are attacking "several projects advocating tolerance and equal rights" in particular. They just happen to be hosted in Codeberg.

espeak default voice backend is synthesized without using actually real voice samples. So it doesn't require downloading a huge package for each language, which is convenient in some cases, but the outcome is extremely robotic.

You can use MBROLA as backend for espeak so that it uses some voice samples and the result should be less jarring (it'd still be easy to tell it's not natural voice, but at least you'd be able to understand it better). There's a tutorial on this here: https://github.com/espeak-ng/espeak-ng/blob/master/docs/mbrola.md

Or you can try piper (https://github.com/rhasspy/piper) it's one of the most natural-sounding TTS (here are some samples).