AFAIK, it doesn't matter who serves the ads. It's a low-quality page.

I'm sure that serving you a lot of ads is the point of the excessive length of internet recipes, but there's another reason, too. A simple list of ingredients, or a list of instructions (like how to build Ikea furniture) cannot be copyrighted. I think many of these overly verbose recipe authors really do want to make it appear that their own takes on the recipes are distinct and innovative, and that helps them secure their own content from being scraped wholesale. But of course, AI just says, "fuck it, I can summarize," and it's pretty hard to prove it was your recipe it summarized..

I don't understand how decreasing import to the USA has increased buying in Europe. Was there a shortage and more was going to the US? Did they reduce prices in Europe? The article says "redirected a tsunami of cheap stuff into Europe", so I don't quite understand how the tariff in the US has increased buying in Europe.

Follow-up:

I asked claude.ai about this question and it agreed with the position that the GPL not only doesn't impose any obligation on the seller to the buyer, but actively disclaims any obligation (except the obligation to offer source code).

Claude was more thorough than I was, though, and actually looked up the details of the judge's tentative opinion and found that SFC's theory isn't that the obligation arises under the GPL, but that an implicit contract under California law was formed when Vizio's TV's License menu option offered the source code, and Paul Visscher accepted that offer through live chat with Vizio's tech support.

SFC's theory is that this offer and acceptance constitutes the formation of an enforceable contract under California law, and that the court can, therefore, order equitable relief, i.e. order Vizio to provide the source code.

This means the ruling isn't about the GPL at all, and also seems like a really reasonable argument that Vizio needs to cough up the source code to everything their license menu offered. The GPL's only role here is that it motivated Vizio to make the offer through the license menu.

That accords with my understanding, and undermines dskoll's argument that the buyer has standing. The SFC probably needs to pull a copyright owner into the suit to have standing. Unless the SFC is a copyright owner, which is entirely possible. I know they've asked owners of GPL'd code to assign copyrights. I assume some have.

I don't see anything in the text of GPLv2 that says the seller is responsible for ensuring the buyer can exercise/fulfill those rights. It says the buyer has the rights, and it obligates the seller to distribute source code to the buyer, and it says if the seller is under some restriction that prevents them from complying with the terms of the license they may not distribute, but I don't see any obligation to ensure the buyer can exercise the rights separate from the obligation to distribute code to them. But I think that obligation is to the copyright holder, not to the buyer, which means we still have the issue that only the copyright holder has standing to sue.

Your suggestion that the seller be responsible for "fulfilling" the rights might have been a nice improvement to the GPL if it could be written so it achieved your goal of giving the buyer standing, and without creating unacceptably-broad obligations on the seller (a stupid and contrived example: What if the buyer were unable to exercise their right to modify the software because they don't know how to program? Is the seller obligated to train them, or make modifications for them?). I think this might be possible... but in any case it doesn't seem to be present.

If there's some part of the license text I'm missing or misunderstanding, please point it out.

That would have no effect on the fact that the owner of the copyright (which is the original author) is generally the only person that has standing to sue for infringement of that copyright. You would own whatever code you contributed, but since you're saying the result would be an exact duplicate, you apparently didn't contribute anything.

Google's ranking algorithm downgrades sites where content is dominated by ads, so I think the dynamic here is the other way around: Recipe sites layered on huge numbers of ads in order to generate revenue, which caused their search ranking to drop, so then they had to go all-in on SEO to fool the ranking algorithm into raising their visibility.

The goal (not yet achieved, obviously) is to build AI that can learn how to interact with humans the way humans do, not to build machines that need carefully-curated data and instructions. We've had those for three quarters of a century now.

And, I'm sure, millions more who are cinephiles and really enjoy seeing which of the year's movies, actors, etc., are honored. It's stylish here on /. to be curmudgeonly and cynical about popular culture, but there are lots of film nerds who really like this stuff, and it's fine for them to like what they like.

Personally, I like it enough to check out who won the next day, but not enough to want to watch the show. My wife likes to watch it when there's a film she's particularly enthusiastic about and she doesn't have other things she needs to do. I know others who watch regularly, as well as follow the other major awards.

I think this decision will have the opposite effect. I don't know who it is that you think doesn't know how to use YouTube, but my 80 year-old parents watch it all the time, whereas broadcast TV like ABC is become less available in the places it was available, and there's a lot of the world that ABC never reached at all. On YouTube, most of the world will have access.

Yes, exactly. If my power bill goes up because a datacenter was built somewhere in Arkansas, Indiana, Kentucky, Louisiana, Michigan, Ohio, Oklahoma, Tennessee, Texas, Virginia, and West Virginia, then I'd prefer the datacenter to be built where my local tax base can get revenue, in addition to employing people in my county.

>"It's more about who's pants can you get into that will help you get the award."

And meeting the quotas for skin color, sex, able-ness, and sexual attraction of the cast, and "creative team".

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.oscars.org%2Fawards%2F...

I don't get the Rust hatred. C has implicitly had an "unsafe" mode for much longer than Rust.

If you're a C kernel developer, you can jump on the Rust bandwagon very easily: just put the keyword unsafe in your comments and you can write code just like Rust developers.

Maybe, just maybe, this mistake was caused by the fact that the same sort of people who are likely to write bugs into their code are the same types of people who prefer "safe" languages because understanding the subtle nuances of how computers work is difficult. They would prefer a system where they couldn't make mistakes, rather than a system where they had to understand the code and the machine to a high level. There's a place in the world for these sorts of people, but it's not in OS/kernel development. The sort of I-can't-make-mistakes-with-Rust mindset probably lulled the coder into a false sense of security, with the predictable outcome.

Oh. The media made it sound like a lot more. But it has the potential to be a LOT more and FAST if they don't slap on high tariffs or limit the numbers.