111–120 of 163 posts
Dropping timestamps is very akin to using terse catchy titles, it draws in the unsuspecting and gives content wider/longer exposure.
Give context in titles. (The post is a size of a tweet about using them on publications.) Don't make me click to see if I might be interested in opening this content. Dropping timestamps is very akin to using terse catchy titles, it draws in the unsuspecting and gives content wider/longer exposure.
Give context in titles. (The post is a size of a tweet about using them on publications.) Don't make me click to see if I might be interested in opening this content. Dropping timestamps is very akin to using terse catchy titles, it draws in the unsuspecting and gives content wider/longer exposure.
Normally I would agree with you, but the "In fact, this extends to almost anything online and even offline." is implied by the generality of the title.
If it had said "publication date", which is really what's being asked that would be clear enough.
I’ve found that internal documentation is a great place to put timestamps. People often complain that eg architecture pictures or design documents tend to go out of date, as if that’s somehow a big enough problem to not make them. Instead, consider making whatever documentation seems useful at a given moment and timestamp it with a clear, prominent “this was accurate on yyyy-mm-dd”. It will still be useful a year lat…
Addendum: don’t rely on your git/wiki/document-system for tracking the timestamp. “This was accurate on $DATE” has a very different meaning than “this document was last edited on $DATE”. It might be 2 years out of date but someone fixed a typo last week. Just put a sentence/textbox somewhere with the date. If someone does a proper update, they will proudly edit that sentence too.
Earlier quoted context omitted.
People without a technical background could accept a browser that doesn't display an URL at all. Just put a nice big Button with the Google-Logo somewhere, which for many people is "The internet" and they are happy. And anyone claiming otherwise should riddle me this: How do most non-technical people in the world access "awesomepageireallylike.something"? That's right, they click into the address bar, start typing un…
URL is a central concept in web browsing. Hiding it from users goes against the main usability principle that the user should understand what's going on. One does not need a technical background to understand URLs. Browser hiding URLs is like an OS hiding file system structure from users, because files and directories are "too technioal" for them.
Yes, well, this is how mobile OSs behave and most people don't seem to care or even notice...
>should include a timestamp. In fact, this extends to almost anything online and even offline. This was one of the ideas in the General Semantics philisophy. You don't much hear about it nowadays, it's a pre-war thing. One of the tenants was that you should date expressions. For example, if referring to a person, you'd write "Roosevelt, 1930" because a year later, Roosevelt may behave like a different person altogeth…
1. https://en.wikipedia.org/wiki/Time_binding>
2. https://openlibrary.org/works/OL168124W/Manhood_of_humanity?...>
Earlier quoted context omitted.
Which timestamp is relevant on the body of a Wikipedia article that has been maintained for 15 years, with edits ranging from entire new sections being written to minor corrections of grammatical errors.
All of them, which his why Wikipedia maintains an edit history. At the very least you should provide the inital publish date and last update.
Earlier quoted context omitted.
People without a technical background could accept a browser that doesn't display an URL at all. Just put a nice big Button with the Google-Logo somewhere, which for many people is "The internet" and they are happy. And anyone claiming otherwise should riddle me this: How do most non-technical people in the world access "awesomepageireallylike.something"? That's right, they click into the address bar, start typing un…
URL is a central concept in web browsing. Hiding it from users goes against the main usability principle that the user should understand what's going on. One does not need a technical background to understand URLs. Browser hiding URLs is like an OS hiding file system structure from users, because files and directories are "too technioal" for them.
> Hiding it from users goes against the main usability principle that the user should understand what's going on.
The main usability principle is that the user should understand what matters for them. Seeing the path of the URL is completely useless to 99% of web browsing. Better hide it by default and let power users see it if they want.
Anywhere a time or date is shown, it should also show corresponding time zone.
It's maddening to see a time in any UX and not know what time zone it's in.
And YES, a date shown on its own needs a time zone!