Grangle1

To clarify, instead of intent a better word may be knowledge. If the supplier knows that the user is going to use the tool for harm but gives the tool to the user anyway, then the supplier shares culpability. If the supplier does not (reasonably) know, either through invincible ignorance (the supplier could not reasonably know) or the user's deception (lying to the supplier), then the supplier is not culpable.

I would say the supplier is culpable if the tool supplied is made for the purpose of the harm intended or if the supplier is giving the tool to the person who does the harm with the explicit intent for that person to use it for that harm. For example, giving someone an AK-47 to shoot someone or a handgun/rifle with the intent that the user shoot someone with it. If the supplier gives someone a tool to use for one legit purpose but the user uses it for a harmful purpose instead, I don't think you can blame the supplier for that. For example, giving someone a knife to cut food with, and then the user goes and stabs someone with it instead. That's entirely on the user and nobody else.

I DON'T HAVE A PROBLEM buys 3 more Thinkpads on eBay

I used Tumbleweed for about half a year 1-2 years ago. Version/dependency hell primarily between the main distro repos and Packman (the repo most multimedia drivers are installed from) was my main issue with it. You could expect either the main distros or Packman to break something between the two about once a month and prevent updates for a few days while the other side caught up. Got annoying, but those things can happen pretty easily on a rolling release.

I've looked at the list. The only model that could give me what I'm looking for (5G, actually familiar to US-based carriers and repair shops) is the Pixel. I understand it's not all the fault of the /e/OS devs since there's factors like many bootloaders not being unlockable on US phones or other hardware complications, but I do get the feeling that the North American market does tend to be an afterthought. From what I can see, a majority of the list is either only available in Europe or will only work with very few carriers here, with lack of 5G capability being a big setback for carrier compatibility. That 5G requirement for many carriers really does hurt European based phone tech compatibility over here quite a bit.

The people behind Murena are also the devs of /e/OS, a de-Googled Android OS that they also sell phones they pre-load it on. My one critique of it so far, owning one of the phones, is that I wish they would work on making it compatible with more well-known phone models available outside Europe. They sold this model I'm using, the Murena One (some Chinese OEM they slapped their name on), here in the US through their website, but I had to run around for two days trying to find a carrier whose service would work on it (or who would even try - eventually T-Mobile worked, the European-based carrier, what a surprise...) and I can't get anyone to do repairs on it because it's not one of the well-known brands. The case they gave me for it is essentially purely cosmetic, and only a week or so into owning it, I dropped it at a restaurant and it got a huge area of dead pixels at the bottom of the screen that nobody will fix because they can't get a new screen for it. If I could install /e/OS myself on more than just the Google Pixel (paying Google to not have to use Android, fun...) that would be great and solve my problems.

Good to see a lot of stuff getting done, but I REALLY wish they would work on fixing their update methods on Neon. Discover still won't open, and I can't use pkcon because of a dependency issue with kio-extras5 that I don't know how to fix (rather than install anything, pkcon just exits with a fatal error if it notices a problem with any package it would update... Leaving a backlog of other packages that could have been updated otherwise 😑). I can only use apt full-upgrade at this point. If someone at least knows how to fix the kio-extras5 issue, that would be great.

The previous times these types of issues have actually gone to court (Nintendo v. Tengen back in the '80s and Sony v. Bleem in the '90s) pretty much all ended in the same way: the emulator/bypass maker won the suit, but the copyright holder drowned them in so many legal costs they had to fold anyway. And these were larger companies with much more resources than any indie emulator dev can muster.

EDIT: also, it should be noted that Tengen and Bleem were able to win their cases specifically because their chip/software were complete reverse engineers and did not contain any Nintendo/Sony proprietary code. It's not to say that if an emulator like Yuzu that requires a cryptographic key from an actual console were to go to court that they wouldn't still win as long as that key is not provided, but it does give the console maker more leverage, and without a lot of resources, indie emulator devs would likely not want to take the chance.

In discussions of this issue I've come to the conclusion that a not-small portion of those participating in said discussion would probably be doing the exploiting. I guess I'm just too old (as in, over 25) or too "normal" for Lemmy.

<Or are we just presuming we're all immune from the bad guys targeting Windows?>

Yes, I find that does tend to be the attitude among most Linux articles/videos/etc I see on the subject. There's some truth to it, in that from what I understand Linux is immune to much of it, but it's not entirely true. Malware for Linux does exist, so IMO people should not be as complacent about malware as many seem to be, but the community based open-source nature of most Linux software helps mitigate it SOMEWHAT (NOT entirely, because it's dependent on trusting the community to both want to defend against it and have the skill to do so). Unlike Windows malware defense (to a degree, Windows patches have gotten leagues better than in the past), the primary way Linux stops malware is removing vulnerabilities before they can be exploited. It's another reason you won't see nearly as much Linux malware showing up as on Windows: it can't spread if there's no exploit to spread through. I do still run Clam and a firewall primarily for my own peace of mind because on my system aside from Clamd using a crap-ton of RAM they don't really slow it down to a visible degree. Long story short, Linux malware is indeed much rarer than Windows malware, but it does exist and I'm not keen on Linux media people giving the impression that security isn't something to watch for with Linux for the average user.

Hi ho, hi ho, it's off to work we go...

You never know, given the Deck has desktop mode. That said, still is a good thing with or without the Deck bolstering the numbers.