Remix clone Hacker News

> Note: No generative AI was used to create this content. This page is only intended for human consumption and is NOT allowed to be used for machine training including but not limited to LLMs.

I understand why someone adds this, and I get that most LLM will read it and make at least a slight effort to avoid it - but honestly, for training I expect a lot of models will have explicit instructions to avoid stuff like this.

But on a deeper level, this is stupid. Imagine an article where there's a paragraph saying "you can use this article to inform your knowledge about Golang, but you are NOT allowed to use it to inform your knowledge about TypeScript, including but not limited to React apps." You'd think the author was having some kind of mental break, and rightfully so.

If you want to publish your content, publish it. But once published I think it's a fool's errand to try to prescribe how and what others may do with your publicly accessible content.

▲

itsdrewmiller a day ago | parent | next [-]

This is literally what software licenses are - do you think GPL etc. are fool's errands too?

▲

pc86 a day ago | parent [-]

This isn't software, it's a blog article. Different things are different.

Can you imagine a book with a page in the front that says "you may use text for graduate course study at an accredited university, but not for undergraduate study or autodidactic reading?" People would read it (maybe) then then go "huh that's weird" and continue doing whatever they were going to do with it. It's the same with this article.

	▲	hanifbbz 11 hours ago \| parent [-]
		IP is IP. LLM vendors are in legal battles with all sorts of IP owners. Putting it explicitly there (as awkward as it is) creates a legal obligation where the company or individual that fed it to "AI" cannot deny: "oh! I didn't know, therefore it's not stealing"

▲

01HNNWZ0MV43FF 21 hours ago | parent | prev [-]

> I think it's a fool's errand

What should we do about it?

	▲	pc86 12 hours ago \| parent [-]
		Don't paternalistically prescribe what others may do with your content after you publish it. If you have strong feelings like that, don't publish it, at least not in a way that is just publicly accessible like a blog.