KeePass can do TOTP, it’s better to have a separate database for those for obvious reasons, though.

Pretty much.

Imagine you have 3 employees working 6 hours screwing screws. Suddenly you find out about a magical screwdriver that makes them finish their 6 hour shifts in just 2 hours. The fair thing to do would be to buy 3 screwdrivers and make your employees work shorter shifts for the same money. Maybe give them a proportional raise and make them work 4 hour shifts.

But if you think in terms of maximizing profits, of course that’s not what you’ll do.

Instead, we fire two employees, cutting our costs, buy only one magical screwdriver, cutting our costs again, double our last employee’s salary, which is still less than what we paid our 3 employees, but if the remaining employee is not looking at a bigger picture, they are happy (100% raise!) and then we make them work 8 hours instead of 6 (you are getting much more money now, right?)

All in all, instead of benefiting the working conditions, an introduction of a better tool lead to more money in the pocket of the CEO, two unemployed screwdriver drivers and one that screws four times the screws for only half the money per screw.

Profit-driven economy is just slavery with extra steps.

I usually don’t go out of my way to explain privacy to people, but I have to explain to almost every new acquaintance that I don’t have to have a particular reason to refuse being in photos. One of the most egregious cases went in the line of “I hung out with that kind of famous guy once and he asked me not to post pictures of him, I can understand that, but why would you, a nobody, refuse being in pictures!?”

Saddest part is that even people who agree to not take pictures of you without further explanaion will usually throw quips at you every time there is a camera nearby.

Too bad, doesn’t work in my elinks.

There are projects like RedoxOS that are slop-free, but as it is not that mature, it’s quite a bit of work to set up. It’s also implemented in Rust which is not as bad as some other projects with it, but still not free of slop.

What I see is them asking whether or not their users want to see “AI” in Audacity and that sounds like a perfectly fine thing to survey for. There is also an option for a custom response, go answer with something like “I will stop using Audacity if AI functionality gets implemented” if you care about it.

On the other hand, I think Audacity has been using LLMs on the development side for a while now and Tenacity exists with a clear no-slop policy.