The problem with a registration-based system is that the immediate logical reduction is to a git push hook that notifies the copyright office each time I push t

The problem with a registration-based system is that the immediate logical reduction is to a git push hook that notifies the copyright office each time I push to a public project on GitHub. Nobody is prepared to build that server farm. And that's just for our industry; I can't imagine what kind of copyrightable data is produced on a daily basis in, say, engineering or science. I'm on board with charging renewal fees for copyright, but you have to do it with a "five years after publication freebie" clause. I'm not going to file for protection on the 20 or so small projects I work on each year. Keep in mind--lesser OSS projects will fall out of copyleft under this system, because now copylefters have the same fee structure that copyrighters do, but not the business model that goes with it. So, depending on your view of copyleft, this can be good or bad.