It's a fine line that's been drawn, but this ruling says that AI can't own a copyright itself, not that AI output is inherently ineligible for copyright protection or automatically public domain. A human can still own the output from an LLM.
The argument is that converting static text into an LLM is sufficiently transformative to qualify for fair use, while distilling one LLM's output to create another LLM is not. Whether you buy that or not is up to you, but I think that's the fundamental difference.
This is a well known blindspot for LLMs. It's the machine version of showing a human an optical illusion and then judging their intelligence when they fail to perceive the reality of the image (the gray box example at the top of https://en.wikipedia.org/wiki/Optical_illusion is a good example). The failure is a result of their/our fundamental architecture.
I still can't believe the guy went to Indonesia, went into the monkeys' habitat, gained their trust, set up the camera on a tripod in a way the monkeys would have access to it, adjusted the focus/exposure to capture a facial close-up -- basically engineered the entire situation specifically for that outcome, and simply because he didn't physically hit the shutter he lost credit for the photo. Meanwhile I can open my phone's camera, spin around three times, take a photo of whatever the hell happens to be in its viewfinder and somehow that is sufficient human creativity to deserve copyright protection.
To me, this is at the heart of why Trump won this election. I honestly do not believe your grocery bill has tripled. That's 200% inflation, which is an insane number. The statistics we have are that groceries have gone up ~25%. I have such a hard time imagining any combination of products that would add up to 8x the national inflation average of groceries.
But, I also don't think you're lying. I think you honestly believe your grocery bill tripled, and I think a lot of people have a similar internal impression about how bad inflation got. It's not useful for me (or, for politicians) to try and argue it logically. No one can check your receipts from 2019 and 2024 and say, look, things aren't actually that bad. Dems needed to kind of take it at face value and come up with a solution to something that people feel is real, and they just did not do that.
As someone with the same name as a somewhat well-known former Bitcoin developer, this is sort of a latent fear I have. I would expect that someone dumb enough to think a home invasion is a good idea is also dumb enough to not double-check whether they've got the right guy.
It's extremely weird to see this site on HN! I built this site in 2014 -- and haven't touched it since. I wasn't a developer then, I was a product manager, and this was a "look, hiring managers, I can build things" side project (it worked, I've been a dev since 2016).
Despite being about 40% broken I keep the site up because it's still reasonably functional and there are a surprising amount of sites that now depend on having hotlinked the patterns directly from this domain. If it ever degrades to the point of being actively dangerous (and the attribution link rot is pretty close), I'll shut it down. Until then, it's a fun relic from the internet of a decade ago.
Just to answer a question upthread (and I 100% agree this should be on the website), the patterns are all CC-BY-3.0, meaning it just requires attribution and any pattern can be used for free.
"Every artist, performer and creator on Patreon is about to get screwed out of 30% of their gross revenue"
Does Apple have access to Patreon creators' gross revenue? I thought they only charged commissions on payments through IAP, which I assumed is only a minority of their overall gross.
I can be that guy. I use Rewind for Mac, which is almost identical to Recall in functionality. I love it, and I've used it frequently to find things that otherwise would have been lost forever.
Most recently I used it to refresh my memory on a particularly convoluted way to authenticate with a third-party oauth system (it involved using an online oauth debugger and curl commands). I had gone through the process once successfully weeks ago, but by the time I had to do it again I'd forgotten every detail. Rather than have to go through the process of figuring it out again, I went back to my successful attempt, watched it, and basically retraced my steps. Rewind probably saved me an hour or two.
My take on Recall is that, like with almost everything, it's a trade-off of security for convenience. I find it valuable enough that I'm willing to make the trade-off, but others might not.
The article is a little bit hand-wavy about how exactly the database comes to be decrypted and remotely exfiltrated. The headline says it takes "two lines of code" but unless I'm missing it, I don't see those lines discussed in the article.
Not sure I've ever seen a company openly take this position. This is a crazy policy.