This repository was archived by the owner on May 12, 2021. It is now read-only.
Reduce timestamp specificity on profile #1290
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Problem: Concern has been expressed about being able to see granular timestamps on the profile page, which would let you see "active 3 seconds ago" or similar. This is public metadata that anyone can access, and we **can not** provide privacy with UI decisions, but the idea that high specificity in the UI is creepy seems fair to me. Solution: Change the display format so that the options are "Today", "Yesterday", "Last $weekday", or the default date formate for the locale in question. Since we aren't hardcoding strings, this should continue to be localized.
Contributor
|
Although the "added privacy" is nice (albeit an illusion) I'd say the bigger reason for this change is the mental health of the reader (of the timestamp). To quote hoodownr, "I hate other social media where people stalk each others online activity, he was on 3 minutes ago, why there is no like on my funny cat video? blah." |
Contributor
|
And thanks for the quick fix :) |
Contributor
Author
|
No problem, patches ftw! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: Concern has been expressed about being able to see granular
timestamps on the profile page, which would let you see "active 3
seconds ago" or similar. This is public metadata that anyone can access,
and we can not provide privacy with UI decisions, but the idea that
high specificity in the UI is creepy seems fair to me.
Solution: Change the display format so that the options are "Today",
"Yesterday", "Last $weekday", or the default date formate for the locale
in question. Since we aren't hardcoding strings, this should continue to
be localized.
https://momentjs.com/docs/#/displaying/calendar-time/