Ask HN: Should AI trained on publicly available data be banned?

Ask HN: Should AI trained on publicly available data be banned?

The creators DALL-E and Github Copilot -- and people in favor of training AIs on publicly available data in general -- argue that people have been studying and making derivative work since the dawn of history, so there should be no problems training these models on public art and OSS software. There are many IP and copyright laws and precedent cases addressing whether a derivative work is allowed, and the images and code snippets these AIs generate seem to satisfy all of them. They are trained on publicly available sources, are not identical copy, are not clearly attributable to any original author (unless explicitly prompted to), and the AI model is incapable of having clear intention of copying when the work is being generated. These are all valid points, and certainly the lawyers at Microsoft and OpenAI can argue in favor of them better than me.

The problem is these laws were created when creating derivative work was not scalable.

Just a year ago to create a painting you have to spend years learning how to paint, studying the works of the old masters, making and improving your own works. Each new paintings take less time than the last, but the hours dedicated to create new work, either a masterpiece or a book cover, is never insignificant. To create a variation take almost as much time. To change to a new style you have to start the learning process all over again. It is hard, but you put your personal time and efforts to it. If your work was inspired by others, as long as it is not a blatant copy, the original authors will certainly feel appreciated, even if they may not like it.

Now all it takes is a text prompt and a few clicks, and you can create images in any style, from any author, with as many variations as you want. Code snippets generated by Copilot is not currently in the same league, but I think we can all agree that it is only a matter of time before a whole project can be created with a requirement prompt, certainly in the same style as the author or authors of the individual packages the AI was trained on.

The difference is industrial scale harvesting of creative efforts. Somebody admiring your works and spend time and efforts trying to learn from you is okay. If they become famous and make a lot of money you will be credited as their inspiration and at least an influence on their success. An AI blindly scanning and blending and making mass copies of altered works to make a corporation rich is not; in the corporation's eye the original authors, from the old masters to the modern amateurs, are all no different than unpaid slaves producing textiles in a mill somewhere to be fed into a machine to create mass produced clothing.

Sure all the training data are taken from publicly available sources with permissive license, but those licenses are created when we still think creative arts will be the last AI frontier, which wasn't event that long ago. If you could have foreseen that the license you chose back then would allow a corporation to profit from your work, would you have made the same choice?

So I would argue that from now on, training AIs on publicly available data must be banned, except where the work is on public domain or where the license explicitly allow the work to be fed as training data for AI models. If a law is not explicitly passed, current permissive licenses such as Creative Commons should be revised to include a clause addressing this point and let the author decide whether to let AIs train on their work or not.

I feel like having such a law or licensing convention established as soon as possible will greatly benefit humanity in the long term. In the short term we all want more free content, but once AIs start taking over all jobs now performed by human, creative arts will be the only source of meaning left for us in the future.

Discussion 9 comments · 3 points · lvnfg · 2022-07-25
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.