Hacker News new | past | comments | ask | show | jobs | submit login

That would be such a limp remedy. It's basically just what can be done right now without the legal blessing.

Rather what we really need is that in order to qualify for copyright protection at all, source code (ie the original creative work) should be put in escrow. When the copyright expires or the work is abandoned, then the source code gets published as part of the public domain.




And it's at that point the escrow code is found to be incomplete.


Fines, losing the ability to copyright things going forward, bonding/insurance, verification that the published works are derived solely from what's in escrow. There are many ways to regulate enforcement. It's very odd to point out the possibility of attempts to skirt the law as a reason to not consider such law to begin with.


For software, you’d need to archive the whole build process too. The dependencies have their own issues with bit rot.


Sure, but ideally copyright terms should also be short enough for that to not be a big issue.


Lol if you've dealt with the NPM ecosystem at all, you've seen builds break in months, and even the most avid copyright reformers don't want terms that short.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: