undefined | Better HN

0 pointskeeda2mo ago0 comments

> What do you mean?

People are taking screenshots of existing products and feeding them to AI to reproduce them from scratch. From this site: https://ghuntley.com/real/

> Any product features or platforms that were designed for humans. I know that's going to sound really wild, but understand these days I go window-shopping on SaaS companies' websites for product features, rip a screenshot into Claude Code, and it rebuilds that product feature/platform.

Also this comment where backend code could be reproduced wholesale from the APIs: https://news.ycombinator.com/item?id=47259485

And this whole thread about relicensing AI-rewritten open source projects: https://news.ycombinator.com/item?id=47257803

> Patents aren't going to cover the vast majority of what exists as code because patents only cover inventions and not common every day code.

Agreed, but as we're finding out, everyday code is now cheap enough that there will be questions about how much of it is worth protecting... and, given the unclear stance on AI-generated code, maybe even if it is protectable at all.

Yes, the bar for patents is way too high for every day code, but you can always get one by making the claims narrow enough. I think that will actually serve one of the underlying goals of patents by incentivizing people to build things that are actually novel and non-obvious rather than just a slight variation of another project.

For projects where there is absolutely nothing technically novel (which is rarely true, cf "claims narrow enough") moats could be in hoarding data, network effects, and the like.

Note, I'm not necessarily happy about all this, this is just how I think it could play out absent larger changes to IP laws.

0 comments

freejazz2mo ago

>Also this comment where backend code could be reproduced wholesale from the APIs: https://news.ycombinator.com/item?id=47259485

Do you mean deduced instead of reproduced?

>Agreed, but as we're finding out, everyday code is now cheap enough that there will be questions about how much of it is worth protecting... and, given the unclear stance on AI-generated code, maybe even if it is protectable at all.

AI generated code is likely not protectable at all under copyright, but that was expected by anyone who follows this area of the law seriously.

> Yes, the bar for patents is way too high for every day code, but you can always get one by making the claims narrow enough.

Not really, and if you did it would likely not be enforceable because the getting past a §101 motion isn't likely.

>Note, I'm not necessarily happy about all this, this is just how I think it could play out absent larger changes to IP laws.

I'm not sure any of it is a bad thing. Why should AI generated code be protectable under copyright? It can still be protected by trade secret, which seems fairly sufficient for what it ultimately is.

keedaOP2mo ago

Yes "deduced" makes more sense, though I guess the code was not really the point. I really should have said the backend functionality is being reproduced. As copyright doesn't protect functionality, the closest proxy we had was the code itself, and now that is meaningless.

> AI generated code is likely not protectable at all under copyright, but that was expected by anyone who follows this area of the law seriously.

I haven't followed too closely, but the ruling on AI art seems to leave the door open for "significant human creative input" like "editing, arrangement." This leaves room for photography, but can also be covered by "architecture, followed by iterative prompting and potentially manual editing to refine the code", which is still needed for any non-trivial AI-generated code.

I think the situation is not great because the law is too fuzzy and outdated, and could allow for "AI laundering" of copyrighted works, as the relicensing thread suggests, which is especially not great for open source where trade secrets are not an option.

> Not really, and if you did it would likely not be enforceable because the getting past a §101 motion isn't likely.

Not a lawyer, but I've seen tons of such issued patents out there, and many have even been upheld in lawsuits. §101 is often trivially bypassed adding "computer readable media" or some "non-abstract side-effect" language to claims. Like, one pattern of claims is "A method of - algorithm - algorithm - algorithm - show something to the user / write to a DB / transmit a message / etc."

freejazz2mo ago

>Yes "deduced" makes more sense, though I guess the code was not really the point. I really should have said the backend functionality is being reproduced. As copyright doesn't protect functionality, the closest proxy we had was the code itself, and now that is meaningless.

But is was only ever so meaningful because as you point out, copyright does not protect functionality.

> I haven't followed too closely, but the ruling on AI art seems to leave the door open for "significant human creative input" like "editing, arrangement." This leaves room for photography, but can also be covered by "architecture, followed by iterative prompting and potentially manual editing to refine the code", which is still needed for any non-trivial AI-generated code.

I don't think this kind of analogizing does anyone any benefits tbh.

>Not a lawyer, but I've seen tons of such issued patents out there, and many have even been upheld in lawsuits. §101 is often trivially bypassed adding "computer readable media" or some "non-abstract side-effect" language to claims. Like, one pattern of claims is "A method of - algorithm - algorithm - algorithm - show something to the user / write to a DB / transmit a message / etc."

I can't agree with this observation, unfortunately.

keedaOP2mo ago

Generally my concern is copyright was an imperfect but reasonable way of protecting the value provided by code, but that is being undermined.

> I can't agree with this observation, unfortunately.

Interesting, I don't mean to impose, but I'm curious as to how things have changed... could you point to a representative case (maybe eg a patentlyo article) that I could look at?

j / k navigate · click thread line to collapse

0 comments

freejazz2mo ago

>Also this comment where backend code could be reproduced wholesale from the APIs: https://news.ycombinator.com/item?id=47259485

Do you mean deduced instead of reproduced?

AI generated code is likely not protectable at all under copyright, but that was expected by anyone who follows this area of the law seriously.

> Yes, the bar for patents is way too high for every day code, but you can always get one by making the claims narrow enough.

Not really, and if you did it would likely not be enforceable because the getting past a §101 motion isn't likely.

>Note, I'm not necessarily happy about all this, this is just how I think it could play out absent larger changes to IP laws.

I'm not sure any of it is a bad thing. Why should AI generated code be protectable under copyright? It can still be protected by trade secret, which seems fairly sufficient for what it ultimately is.

keedaOP2mo ago

> AI generated code is likely not protectable at all under copyright, but that was expected by anyone who follows this area of the law seriously.

> Not really, and if you did it would likely not be enforceable because the getting past a §101 motion isn't likely.

freejazz2mo ago

But is was only ever so meaningful because as you point out, copyright does not protect functionality.

I don't think this kind of analogizing does anyone any benefits tbh.

I can't agree with this observation, unfortunately.

keedaOP2mo ago

Generally my concern is copyright was an imperfect but reasonable way of protecting the value provided by code, but that is being undermined.

> I can't agree with this observation, unfortunately.

Interesting, I don't mean to impose, but I'm curious as to how things have changed... could you point to a representative case (maybe eg a patentlyo article) that I could look at?

j / k navigate · click thread line to collapse