3 ms·
If you are going to update the date every year (regardless of whether or not there has been any change to the work), you should probably make it something like
by tzs 4y ago
If you are going to update the date every year (regardless of whether or not there has been any change to the work), you should probably make it something like "© 2010-2023", where the first year is the earliest copyright year for any copyrighted material still in the work.
If you just have "© 2023" you might run into this scenario. In 2018 I rip off your site and include that material in my site, which is © 2018. In 2023 you become aware of this and sue me for copyright infringement.
At trial my lawyers are going to find a way to get my © 2018 notice and your © 2023 notice in front of the jury in a way that suggests mine was first and you ripped me off.
Your lawyers should be able to easily deal with that, but they might have to do things like show both sites from archive.org or something like that, and take time to explain what archive.org is, how it works, and why the jury should believe that when archive.org says that a site contained certain content on a certain date it should be trusted.
This takes time. In a civil suit court time is limited. Each side has a total time budget for their opening statement, examining witnesses, cross-examining witnesses, and closing arguments. If my lawyers can make your lawyers have to go spend time explaining archive.org to the jury, that's good for us.
And yes, your lawyers will probably have to explain how archive.org works because during jury selection mine will have worked to exclude jury members who are already likely to know that. We should be able to get at least a few people on there who are going to need it explained.
Oh, and my lawyers will also probably be able to get in a suggestion that the fact that your site said © 2023 on it means you were trying to be deceptive about the copyright maybe to illegitimately squeeze some extra years out of copyright protection. That might prejudice the jury against you on anything that is close.
If you had said © 2010-2023 all those potential ways my lawyers can make yours waste time or make you look shady go away.
- lioeters 4y ago> If you had said © 2010-2023 But couldn't someone copy my site and change the starting year to earlier, like © 1998-2023? Then my lawyers would still need to explain archive.org to the jury. Even then, I have a feeling that archive.org is not evidence of anything. (Well, may be enough to convince a jury.) For that matter, the content of any website - or even anything digital - seems like flimsy evidence to support historical fact, since it can be changed at any time. Perhaps this is where someone mentions the blockchain as "immutable proof".
- jjk166 4y agoWell the real solution if you want to actually utilize copyright protections is to register the work. This creates a dated government record. In the US (which is admittedly a bit of an oddball), to file a copyright infringement suit, you need to have a registered copyright. No one can get a registered copyright on your work if you've already got one (well they might be able to get one if there is a clerical error but it would definitely be dated after yours). Without a registered copyright you can still defend yourself from an infringement suit by showing your work predates theirs, but you can't really go on the offensive. You can send cease and desist letters but that's about it. You can't collect statutory damages or attorney's fees. In most other countries a registration will at least create the presumption of authorship, meaning the other party is obligated to prove their work came first. But yeah, putting the year on the copyright notice does nothing.
- dahart 4y agoTIL! I didn’t know registration was required in order to seek damages. That sounds suspiciously like a loophole that means the US doesn’t quite meet the Berne convention, no? Or we adhere to the letter of the convention but not the spirit? Looking around, I like how a lot of countries have no voluntary procedure for registering copyright, that seems more in line with the intent behind Berne.
- alexfoo 4y ago> "© 2010-2023" In the bit of Big Blue that I worked in this is what we did. You only updated the later year if you made a non-insignificant change to a file. Fixing a simple typo in a comment wasn’t enough, nor was just reformatting/moving code. Fixing a bug, changing a user visible string, refactoring, adding a new feature, etc and you’d bump the “to” year. I think there was also some kind of magic rule that you could put the next year (e.g. 2023) from some point late in the current year, something like you could add 2023 if it was November 2022 or later. Don’t think I ever saw these “rules” formally written down so everything was just a kind of folklore passed on from one generation of devs to the next. Copyright years in version/help output was definitely updated as part of the build/release process.