Amazon is a party to interactions with their website. That gives them standing to sue over those interactions. Whether they can sue Perplexity specifically is what was being debated in these motions.
Nah, once you have the bits on your device you should be free to do with them whatever you want. Amazon doesn't get to dictate how you consume what they give out for free.
What you think you should be able to do with the data you get back from contacting Amazon’s servers doesn’t impact whether Amazon has standing to sue you over how and why you contacted their servers.
Sure and what you comment doesn't change that people have opinions about the validity of such cases. Amazon cares more about their bottom line than the health of their workers, we should be highly skeptical of anything they want to do as there is a strong chance that it will hurt + immiserate workers.
Not all of us have the same bathroom fetish as Bezos.
Sure it does, you're making a lot of assumptions here. The most egregious one is believing that that I think the legal system means anything to actual justice and not a system that is mostly used to protect the interests of the elite at the expense of the poor.
Because David Ellison’s explicit plan is to run Warner Bros. Discovery (owners of CNN) and Paramount (owners of CBS) as two divisions within Skydance Media. He committed to keeping a 20-odd film slate at WBD as part of antitrust negotiations with the U.S. and other countries. So he has to keep the studio running while figuring out how to pay off the investors with depreciating Oracle assets.
All I’m saying is that if your idea of driving a car is to sit on the engine compartment and pull levers and cables from there, you might have a different experience than most drivers.
More that my motherboard came with a Broadcom WiFi chip instead of MediaTek which everyone recommends for Linux, and the shipped Linux drivers can only use 1 of the 4 antenna and won't connect to any 5ghz networks.
It "works" with 2.4 with 1 antenna, but the speed is then capped at 150Mbps instead 600Mbps/1300Mbps the hardware is capable of.
So it's like buying an AWD car, but realizing only one wheel gets power. Still technically drivable, but hardly working well. Maybe most people wouldn't even notice at all, but I figured I was technical enough to get in the weeds and fix it. Not all cars end up being Toyotas, sometimes you get a Jaguar.
I use Linux mint on my desktop. Wifi just works. I’m using some X870 motherboard.
I got the motherboard when it was really new, and I think it took a few months before wifi worked properly in mint out of the box. (I use Ethernet anyway so it wasn’t too upsetting). But after a few months, they had it all sorted. I have never manually compiled a kernel or wifi drivers or anything on this machine. I suspect most Linux users don’t do stuff like that any more.
Not to say it’s a trouble free experience. I’ve had problems with the nvidia drivers a few times recently. In the transition to nvidia’s new driver model, I’ve somehow ended up with incompatible nvidia packages on my system and the graphical environment broke. The most recent time I asked Claude code to take a look at my system and tell me what commands I should run to fix the nvidia packages. It did a great job.
It doesn’t feel like a kit plane any more. It’s a bit temperamental from time to time, but for the most part Linux just works.
It's compile drivers or research your hardware before you buy it. The latter is highly recommended. If you go against the common advice, it's kinda your problem. If you bought the hardware before installing Linux or it was given to you, well, that sucks. That said, driver problems, especially important ones, aren't that common anymore.
Nailed it. My Linux machine was built from the retired parts from my main desktop, so it very much is stuff that served me well for several years under Windows.
But the advice is still very much to research the hardware or buy a prebuilt with vendor support.
Compared to a decade ago, more stuff just works; especially noticeable with graphics drivers. But when things hiccup, which they still do, it still requires quite a lot of tech savviness to solve.
I can honestly say that I've never had to compile wifi drivers from source in more than a decade of using Linux as my main OS, even through my distrohopping phase. And I'm not researching my hardware ahead of time, either. I don't even know what you'd need to be running in order to have to do that? Maybe void or something similar? I don't think that my experience is particularly unique.
The sharp edges are usually pointing the package manager at a repo (generally an official expansion) that lets you install the necessary binary.
I’m not chasing theoretical portability and checking off a box saying my code is 100% pure ISO C. If that’s important to you, don’t do this (and also don’t use pretty much any allocator!)
Every sufficiently useful C codebase assumes specific implementations.
reply