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

The point of the date it to tell people when the material was created. In some jurisdictions / situations, copyright expires N years after it was created, so that date tells people when copyright has expired.

Unfortunately, in many cases now, copyright is based on the year the author died, rather than the year the work was created, which means it is much harder to work out if something has entered the public domain.

Changing the date without changing the code significantly is arguably fraudulent.




doesn't moving the creation date forward in time make you vulnerable?

if you create some content in 2018 and I rip it off in 2019 and then you update your copyright to 2020, what's to stop me from saying I came up with it first?


That's partly why you have a span like "Copyright 2018-2020" - you are saying some of this material is older, some isn't. You need to keep copies of the older version with the older copyright to be clear which parts were invented when.


I want to like that idea. Unfortunately, I can counter with: When you (as an outsider) see two very similar projects, one claiming to be from 2018 the other from 2020, what will you look into/try out first?


Depends on the selling point. A 2 year old library sounds to me like it's just getting mature.


Obviously the one from 2018. It should still be quite modern but with big issues already ironed out.


> Changing the date without changing the code significantly is arguably fraudulent.

In some countries the publishing date is what counts, and they define publishing for websites as when the site was viewed.


Presumably, even if publishing date is relevant, it's only first publication that's relevant. No work should stay copyrighted forever just because it's constantly being republished.


> it's only first publication that's relevant.

No, the publishing date is relevant (not the first publishing date).




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

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

Search: