4 ms·
Maybe. But we use "last updated" as a useful signal in many, many places, across code, documents and books, and entertainment. We like recent, new, updated st
by mwexler 4y ago
Maybe. But we use "last updated" as a useful signal in many, many places, across code, documents and books, and entertainment. We like recent, new, updated stuff, and we like "authentically old" stuff. As a signal, the date provides value. Having it as "copyright" or simply "last updated" has similar impact in this case.
Sure, no one in the US __needs__ to do this, and there is a cost to it. But the benefit of the signal could outweigh.
Having no date or an old date may send the signal that "the dev team has good legal support", but I wonder how common that perception is. We see from the comments and the parent post that at least the HN crowd has a good chunk of folks who didn't know that date isn't needed.
It's an empirical question to test: does date presence affect evaluation of the object? It would be fun to see. (I would want to try "no date", "last year", "3 years ago", "current year" to see if user perception of the object changes based on presence and time passed).
- leereeves 4y agoNow, having no copyright date may simply send the signal that the team reads HN.
- ghaff 4y agoIn general, a post or article should have a posted or updated date. If I just read your undated 2015 article about how to do $X on a Mac, you've probably just wasted my time. It's probably reasonable to expect a current copyright date on the home page of an active site to indicate that it's current. It probably doesn't need to be everywhere unless it can happen automagically through a template.
- twic 4y agoThe signal it send is that the people who maintain the file do things without understanding them.