Coriza

That is not the purpose of Secure Boot. The purpose is to establish a chain of trust of all code running on the system from boot and as such eliminate rootkits that can hide from the OS. A classic example is the MBR bootkit. Of course that this is mostly out of the window if at some point in the chain the trusted code just runs untrusted code, like the bootloader or the OS running unsigned code. Also the implementation is terrible, a proper implementation would allow the user to use their own certificates and only their own certificates, otherwise a compromised generic certificate fucks everything up like it already happened.

I would prefer to drink something without any sweetness at all than drink something with of this sweetener substitute. Damn, give me a salty drink before an artificial sweetener one.

And you are already trusting Mozilla by using Firefox.

Public transit is common in my 3rd world country and I was surprised how more unsafe it feels in the US. My theory is that it is a by product of the car centric society. For one there is safety in numbers and because it is so underused any one person is more exposed. But also because almost the only people that take the public transit is people who cannot drive or be driven for some way or the other it inevitably have a bigger proportion of mentally unstable people for example.

People it this thread does not know what the Turing test actually tests. It is Ok, I guess the blame fails on pop culture.

The Turing test is not a test of sentience, it is a test if a machine can fool a human being into thinking it is sentient. And machines have passed this test for decades already. Who would have thought that our predisposition to anthropomorphize everything would make us so susceptible to thinking stuff is sentient 🤷

It is. There is limitations to a Turing machine that a human brain does not have. I expand on that on this other comment here.

There’s nothing to indicate the human brain can’t be implemented in a Turing machine too.

That is not true, this is a research branch from computer science and math, it is called Computability theory, it deals with the limits of expressiveness for different types of theoretical machines and expressions, and the most expressive of all is the Turing machine, and a Turing machine cannot do some stuff, the classic example is the Halting problem, a computer cannot definitely say if an algorithm ever stops (mathematica proven that it cannot do it), but a human can do so quite easily.

One may think that maybe a Turing Machine cannot do something but can simulate another machine that does, but that is also proven to be impossible, it cannot simulate something more expressive than itself.

Totally but I also want to point out that reviewing changes is a lot easier than the first review. Ideally it has just a couple of lines changes and they are just version changes most os the time. It also does not help the existence of “pacman for AUR” that just encourages all the bad behavior, they encourage installing a lot of AUR packages without thinking twice, update without checking and to trust it or think it is the same as the maintained main repos since I think most if not all AUR packages also work as a pacman frontend.

The user was never supposed to rely on a lot of AUR packages and if you do maybe you better of with a distro that does package what you need or that the software authors package for.

I will have to defend users here and blame AI scientist/developers together with the whole docker culture. The way they package and delivery software is just terrible. And even though pytourch has support for all GPU apis the devs seems to have a hard time adding this support. Granted, part of that is also on pytourch that for some reason Don’t seem to be able to make a unified release that supports all GPUs and then you need different versions and by default IIRC they default package only supprt CUDA and CPU.

deleted by creator

Kinda off topic and nerdy but because it relates to UI patterns and behavior I wanted to comment:

On git, when you commit a new patch by default it opens up a whole text editor for you you enter your commit message, which incentivize you to write an extensive commit message with title/summary line and paragraph body. If you create a commit on GitHub it just give space for the title and when GitHub shoes commit it also hide the text body even when viewing the whole commit.

The result is people/project who “grew up” using GitHub usually have terrible commit messages and the commit history sucks.

It is worth pointing out that the only reason docx support is lackluster is because of active efforts from MS to undermine third party support. It is a interesting story actually, but I don’t recall exactly, but it goes like this, there was some regulatory push to open formats and MS undermined this by creating and making the docx (and all other *x family) open but make it so convoluted and unnecessarily difficult. If I am not mistaken they even keep unnecessarily updating and changing it so third party is always lagging behind in support and the cherry on top that MS don’t correctly implement its own format on purpose so the files are effectively broken for anyone that follows the spec to a T.

I read about that a couple of years ago, I am speechless that such a thing is even allowed to exist.

Definitely the latter. I unfortunately use a lot of Google services and they are pushing AI integration in everything and making it very hard to opt out or they keep pesting you to enable it.

I “love” when the wrong technology is applied.

On the the dawn of the smartphones Mozilla tried to enter the space with an FirefoxOS and the pitch was that every app was just a website just more tightly integrated with the phone. The problem is that all the web stack is wonderfully resource hog and at the time phones were super underpowered running websites were not optimized in a browser that were not as optimized as today. So it was a terrible choice for the time being.

Other good one was Android early days. They choose Java as the default app environment and development. It kinda makes sense to use it if you want the same program to run on different platforms, the problem, again, it runs worst and with the underpowered devices of the time everything was a slog. And they doubled down on the mistake by using a garbage collector that doubled the memory usage of every app. The cherry on top, at least in hindsight is that arm was and still is the de facto Android plataform, greatly disminishing the advantage of using Java/JVM. And today Google enabled apps with native code optimized for specific plataforms, but everyone only care about ARM so of you try to run Android like in an Intel laptop a lot of apps are not compatible.

End of rant.

This reminded me of a joke patch someone sent to Firefox to rename incognito mode to porn mode.

But there is a difference if it is part of the base experience or unavoidable, like you need a Google account to do anything on an OEM Android Install, like install any app and such. I guess same is true for steamOS, since focus on the OS is the steam app.

Yes, it is the patent shenanigans.

I think that is exactly what they mean, Google abuse/subverting the floss ecosystem creating a de facto closed system, and would have to open up to be a really open source OS if they want to get exempt. Same with apple and the BSD kernel and base (although it can be said that they are not subverting the spirit of the code they use since BSD licenses ate by design made to allow closing the source, etc).

In any case I am pretty confident that all big tech want to eagerly embrace age verification since it is another data point to sell and for their ad machinery.

The biggest hurdle for a Linux phone is proprietary drivers. On a PC you can swap parts, you can add a USB wifi or sound card on a laptop, but on a phone you are kinda stuck with all the stuff on the phone, so the problem with binary blobs is so much worse, and untill we don’t have at least the full drivers source or datasheet as an normal part of phone releases it will always be an impossible to win catch-up race.

At least phones are not getting that much better anymore so is starting to be feasible to floss hackers to fully port Linux to some phones in time for them to still be usable (battery problems a part).