I think this was published in 2010, so not really new - but probably still a possible attack vector.
For as much as Aza brags about his UX expertise, not dating his technical blog posts is inexcusable.
This attack vector is very relevant to this day. It works remarkably well on mobile phones, especially with the new trend of hiding the URLs to save screen estate. Together with throwing up a fake website, you could also try throwing up a fake address bar.
Also with mobile phones you can emulate a native application. This will show when the phone is re-activated with the browser app on.
A redirect to something like a Googleusercontent domain would be tricky, even with a visible URL. The author could also mine the referrer: visitor from HackerNews? Phish the log-in form with a bad gateway message.
If it doesn't have a date, I can't contextualize it, and its value drops.
You can, and should, make the strategic decision that you'll primarily write things which retain their value.
With this, I heartily agree; leaving off a date, though, that's just rude. If there are those who would judge your writing by the date it was written, there's either something wrong with them, or something wrong with the writing. As for the former, you can't do much about them, and probably don't want much to do with them. As for the latter, well, keep aiming higher! The date can be handy, though. Consider it a nod towards transparency and openness, and in more technical pieces with specific instructions, a great boon to those dealing with a version of the software a few years removed.
NO, IT IS NOT
That's probably the stupidest thing I've heard today
Things in IT change all the time. Heck, even non technical things. One text saying something, even if about something pretty "stable", may change tomorrow. It's one of the most important contextual information we have.
I shouldn't have to explain why not having a date is BS so I won't. Time is money after all.
ALWAYS date your texts, and brush your teeth (even though tomorrow someone may come up with something better)
This article, however, probably isn't that out of date - the attack still works!
A marketing best practice; concealing information that might be of positive value to very many users because some users will treat it as a negative input (perhaps incorrectly in some cases, but that's not really important one way or the other from a marketing perspective) has obvious content marketing utility.
That doesn't mean it isn't universally a disservice to thoughtful readers.
No, it is using the observed effect of HN's policy as a piece of evidence for the broader claim that using dates is bad content marketing because it leads people to discount the dated content as it ages; the thesis is that, to maximize the value people ascribe to your content, you should avoid dates.
https://web.archive.org/web/20100527035243/http://www.azaras...