It's not training on copyrighted data that is a violation of copyright. Access to a copyrighted work is not something that is an exclusive right given to copyright owners.

But you know what is (as I quote from the law):

(1) to reproduce the copyrighted work in copies or phonorecords;

(2) to prepare derivative works based upon the copyrighted work;

(3) to distribute copies or phonorecords of the copyrighted work to the public by sale or other transfer of ownership, or by rental, lease, or lending;

What they can get you for is reproduction, derivative works, and especially transmission of the same. I'm surprised it's taken this long to get there. While I am not a lawyer, I suspect Disney has a very strong case here. And believe fines are per instance.

It didn't work through the logic. That is not what these AI's do.

It responded with what a likely stream of tokens would be based on it's trained data and the prompt. That's it. That's all any of this ever is.

I'm not so sure. Take the text of the memorandum.

"increasing the amount of information regarding any risks associated with the use of any such prescription drug"

Is it RFK that gets to determine what risks exist for any particular drug? Are we going to see 'this vaccine may cause autism' messages?

In a normal administration this seems like a decent idea, even if just banning drug advertisements would be better. With this administration, I expect the worst.

The idea that LLMs or any of the current AI tech is anywhere near AGI is laughable.

We're not even in the ballpark of the right technology. We have prediction engines, input consumption systems with internal feedback loops and models.

This is like saying now that we've built bicycles for travel, the next step is to ride those bicycles to the moon.

I'm not part of the kernel development world, but I did read the entire thread that sparked this all off.

There was a patch sent up for some rust code.

One of the maintainers decided to use that patch to take a hard stance on the Linux kernel being C only, not a specific dig on Rust.

The person who submitted the patch tried very professionally to find a solution and address any technical objections on the thread.

Some other people also chimed in, very professionally.

There were some strong words (not directed at any person), but it was mostly professional, even if it was somewhat of a political standoff.

Hector seemed to come flying in off the turnbuckle and go off on a rant that was, at best, tangentially related.

It really seems like Hellwig is ideologically against any language other than C in the kernel and is pushing back on that principle alone.

There's no technical argument against the patch. Hellwig isn't being asked to maintain or work on any Rust code.

It doesn't even seem to be against Rust as a language.

It's basically a hard line of not allowing anything other than C in the kernel.

Agree or disagree about that position, but that really seems like what it is.

You're right, if the goal was to emulate a fly in real time. I don't think we're anywhere near that stage.

We absolutely could do this emulation, and I suspect that will be on the table soon. Yes it would be slow. How slow would depend on how much hardware we wanted to throw at the problem. We're not limited to a single computer, even a single supercomputer. The only thing really standing in the way is money.

BTW, the BIOS and OS are the mapped neurons and connections. There's not something more to it.

Because you are doing what many people do, and what the politically right leaning have purposefully done. Confuse capitalism with well regulated free markets.

Well regulated free markets provide incentive for new products, fulfilling customer demand, efficiently allocating resources.

Capitalism is an economic system the funnels money towards the rich.

If you are in a collision with a large heavy old vehicle such that the forces involved would overwhelm the safety features of a modern car, it doesn't matter what you're driving, everybody is dead.

The person in the large heavy old vehicle is just as fucked, if not more.

The master key doesn't even need to be a key. It would probably be better as an OBD2 plug.

Make the master key an OBD2 plug. You plug it in, authorize on the touchscreen/radio, then you have X amount of time before the auth times out. You could even implement 2FA with that. Need the plug, plus a pin.

The control panels are $400+, the smart dimmer switch is $49. Still expensive, but you can get a 10 pack for $410. Or at least could.

It's not exactly a measure of performance, but if had referenced DOMA he'd at least be in the right decade.

If the story was that one single time, an alien craft made it to earth and crashed, that would be plausible.

Right now, with our current technology, we could put together a ship and make a one way voyage to another star. It would take the kind of focus we haven't seen since the space race, and it would have to be sustained for a bit. We'd have to be okay with people going on a one way trip and not knowing anything that happened until years later. But we could do it. If we could do it, a nearby, similarly situated species could end up here.

An event like that could potentially be kept under wraps enough to be plausibly deniable.

The idea that some alien species has the technology to have dozens to hundreds of craft buzzing around Earth, never publicly announcing themselves, and constantly crashing is laughable.

Although it would be the kind of stories I would spread if I were trying to hid the one time an alien craft did show up... hehe.

Let me know when it can take a distributed system spread out of dozens of repo's, get a question from a user as to why what they are inputting in one spot isn't showing up on the web site, and explain to them what they did wrong and how the system works.

The advantages Rust has over C++ basically boil down to eliminating categories of bugs mostly related to memory problems. No null, no accessing uninitialized memory, no forgetting to dealloc. Bunch of stuff like that. The kind of bugs that account for "70% of security bugs" (you can search that). Also has a very strong type system and the compiler can basically force you to think about all possible paths. It's a common trope among Rust developers that if it compiles, it usually runs correctly.
The costs include (more or less) understanding the memory model. While the compiler errors are extremely well done, you still have to understand that you can't have a mutate after a borrow. Rust is not something where you can slap together a quick and dirty script. That trope of 'if it compiles, it usually runs correctly' cuts both ways. If you forget something, it's not going to compile. You have to understand Rc, Box, etc... and various tools to deal with the single owner aspects of the memory model. There are numerous blog posts our there about "How I learned to stop fighting the borrow checker". Compile times are significantly higher.