5G_activated

You have described, at a high level, passkeys.

Who said anything about not allowing people to say something?

In the real world, if a dickhead spouts garbage you tell them to fuck off. Doesn't mean that they can't open their mouth, just that you don't want them to do it near you. A huge proportion of people online who claim that their freedom of expression is being impinged upon are dickheads who were told to fuck off.

Freedom of expression is not a right to be listened to or to be agreed with.

As it happens, Tor's aim is that they don't know who you are or what you say!

It's not just security updates, there's also whether all the device management tools and techniques, training and institutional knowledge, and customer acceptance will carry over to the new OS. Whether the devices that are within AUE and receive the update are going to run the new operating system well, or they're going to languish with poor performance or broken drivers that will never get another look from the manufacturer because they're 2 generations behind in a vast sea of models and individual configurations.

I also can't find anything online to do with what they're going to do to Chrome OS Flex, so thank goodness I didn't set it up for my mum who was sick to death of Windows 11.

Yet another market that is never going to trust Google with long term support for a product again!

This is true for essentially all Win32 programs too, including the ones that have started to appear in the MS Store. Developers can play in the sandbox from the get go by using Windows Runtime, but no one wants to rewrite their application with a library or environment that Microsoft is going to deprecate and replace in 6 months time.

It's not like Flatpak is perfect, but at least it uses primitives that we understand through containers, and can apply to already existing programs. Even though they were written without playing in the sandbox and might expect full access to services and files, we can fudge it for the most part with bind mounts and open up safer doors through Portal and widget toolkits over time.

Just stop giving LLMs unsupervised access to the computer. No free-form bash tool, no yolo mode or classifiers, and no computer use.

Children were, and are, permitted to use the computer.

I find LLM copywriting revolting, especially Claude's and it is pretty obvious that it is Claude, and even though I might find the software interesting since I own a Clara 2E, it puts such a sour taste in my mouth that I don't want to touch this thing with a 10 foot pole.

If your software is mostly written by the slop machine, fine. I don't have to be upset about it unless I think about contributing and then notice the uncanny nature of the source code. But a website and a README is directly user facing and it is a major disservice, and in my opinion, lack of respect, to generate your website copy with an LLM.

I wouldn't recommend CachyOS personally. If you wish for a distribution with a traditional read and write filesystem and new features and package versions I'd recommend Fedora, which I always end up going back to.

Personal preference, but I like my software to have as little patching or customisation done by my distribution as possible, and to be able to use it as upstream intended. This is a longstanding benefit of Arch Linux, but CachyOS goes beyond this to kit out a default install with garish themes and shell configurations to the point that the default user's login shell gets set to /bin/fish.

Some fume was had because I really do not believe that Shelly is a good choice for the primary system package manager. It's written in C# and compiled with .NET AOT and I just cannot shake the sense that it is an incorrect choice for a core system program.

The GUI needs a little bit of polish, but the command line user interface is terrible; there is a DNF/APT style subcommand interface which has no search subcommand, and other features are split into a Source->Action->modifier "shortcode", but that is very different from Pacman. The action letters differ between sources; for example to search repositories you use "-SQa" but to search the AUR it is "-AS", and I believe that it is like this for the sole reason that no thought has been put into it. I'd also suggest that the authors have little experience with Unix and so it isn't made with the same kind of attitude. There are other things like table wrapping at 80 columns making the output unreadable and lack of a package download counter.

When I brought it up to the "community" I was relentlessly flamed for not being entirely positive about this change to the distribution. I'm of the opinion that the maintainer had her feelings hurt because I criticised her project, and lied about the issues I had raised. A pile on ensued.

The final straw for me that made me dump another 24 hours in moving distribution again is that the attitude of the CachyOS project can be summed up as "script kiddie" and the "community" spaces are populated by and large by children. Despite having the same sort of audience Bazzite has a much more pleasant community. Fedora seems to avoid all of this kind of nonsense, I suppose by dint of being run by professionals, and avoiding Discord.

The point is to get artists to use free software, or enable them to have an alternative to Windows or macOS.

Who was actually using yt-dlp with bun? The primary use is to solve JavaScript challenges sent by YouTube, which uses Deno by default.

To be fair, I'm not quite sure why it would prefer either Deno or Bun when it's far more likely that a user has Node on their system.

there is a long standing problem in Team Fortress 2 where the default FOV is 75, as it was on the console ports of the Orange Box, and it's believed to turn off a lot of new players and enrage regulars because they just don't see things in the periphery that everyone else playing at the maximum FOV of 90 does.

i'd be surprised if there are more users of cachy than bazzite.

what gets missed is that bazzite is, to borrow video game parlance, a mod of fedora's atomic desktops. every piece created to build and maintain the system is on github. it's not rocket science, it's a collection of dockerfiles, rpm specs, config files and github actions workflows. and fedora is not going away any time soon.