Yes, but...in an attention economy, timestamps are beneficial to readers and detrimental to authors.
Ah! yes. The 5th force of nature and strongest of them all -- Force of Incentives.
Use Timestamps
11–20 of 163 posts
Re: Use Timestamps
#12I don't understand how people can accept the browser hiding the URL.
I don’t think it is even possible to display the full URL by default in Safari on iOS.
Re: Use Timestamps
#13It's something that I agree with and increasingly I add dates in my notes. In addition to that, using one single format is really important. if the article was published on say November 2nd. I wouldn't know if it was 11th February or 2nd November. DD MMM YYYY is safest. The 3Ms being Jan, Feb, Mar....
There’s some unexpected behaviour with MMM as a formatter, which is that it’s not always 3 characters long and differ subtle by locale.
Notably on the JVM if your locale is en-GB every month is 3 chars: Jan, Feb, Mar, etc. until you get to September which is Sept.
In en-US it’s just Sep.
Of course, if you don’t specify the locale in code, it will choose the system default leading to lovely region specific exceptions for your servers in Ireland and England.
Re: Use Timestamps
#14I don't understand how people can accept the browser hiding the URL.
I don’t think it is even possible to display the full URL by default in Safari on iOS.
I don’t know which model you have, but on mine you wouldn’t even have the space to display more than a 5-6 characters after the domain name.
Re: Use Timestamps
#15It's something that I agree with and increasingly I add dates in my notes. In addition to that, using one single format is really important. if the article was published on say November 2nd. I wouldn't know if it was 11th February or 2nd November. DD MMM YYYY is safest. The 3Ms being Jan, Feb, Mar....
YYYY-MM-DD is the only correct format and I will die on this hill
The most nonsensical approach is what the Americans use but let's not go there : - )
Re: Use Timestamps
#16It's something that I agree with and increasingly I add dates in my notes. In addition to that, using one single format is really important. if the article was published on say November 2nd. I wouldn't know if it was 11th February or 2nd November. DD MMM YYYY is safest. The 3Ms being Jan, Feb, Mar....
YYYY-MM-DD is the only correct format and I will die on this hill The most nonsensical approach is what the Americans use but let's not go there : - )
The fact that this sorts correctly seals the deal. There is no better option.
Re: Use Timestamps
#17I think it depends on the kind of article. Some articles are timeless. So that's why I put the date at the end.
Re: Use Timestamps
#18Amen to that! It's really frustrating when a date is not put there, especially on tech topics. If no tech version is written explicitly either, you are left wondering "will this still apply to my case or is it something super-old?" But beside selfish use-cases like looking for an answer to a problem, it is something that was already solved in the previous form of knowledge distribution: books. Why do we always take o…
> But beside selfish use-cases like looking for an answer to a problem, it is something that was already solved in the previous form of knowledge distribution: books. Why do we always take one step back when moving forward?
Note that with book you have the publication date, but you don’t know when each chapter was written. This doesn’t matter for most books, but for highly technical subjects it may matter.
Re: Use Timestamps
#19It's something that I agree with and increasingly I add dates in my notes. In addition to that, using one single format is really important. if the article was published on say November 2nd. I wouldn't know if it was 11th February or 2nd November. DD MMM YYYY is safest. The 3Ms being Jan, Feb, Mar....
You can just use ISO 8601, YYYY-MM-DD, then you can be international standards compliant as well.
Re: Use Timestamps
#20I don't understand how people can accept the browser hiding the URL.
Firefox seems to always display the url after the protocol, even on mobile. I don't like the protocol omission, but I've grown to tolerate it.