That reminds me: we should demand Fediverse stuff display proper timestamps. Even now, your comment is showing as “41m [ago]” for me viewing it in Voyager, which is just being part of the problem for no good reason.
Agreed. The invasiveness of the change definitely depends on which UI you’re talking about: in the default web UI it’s probably no big deal, as there’s typically a ton of dead space to the right of the message and you could use the css @media rule to turn it on and off depending on width or something if you wanted, but in a mobile app it would be more problematic.
It’s too bad there’s no @media type 'screenshot' so that we could change the formatting to show the absolute timestamp automatically upon taking a screenshot. (Then again, it would probably be too exploitable anyway…) Especially for apps, I’m liking my “add a dedicated screenshot function that reformats automatically” idea more and more.
That reminds me: we should demand Fediverse stuff display proper timestamps. Even now, your comment is showing as “41m [ago]” for me viewing it in Voyager, which is just being part of the problem for no good reason.
in terms of compactness, it’s faaaaar more verbose to display time and date
i’m not necessarily disagreeing, but it’s a significant change and would likely need more than a simple text change
Agreed. The invasiveness of the change definitely depends on which UI you’re talking about: in the default web UI it’s probably no big deal, as there’s typically a ton of dead space to the right of the message and you could use the
css @mediarule to turn it on and off depending on width or something if you wanted, but in a mobile app it would be more problematic.It’s too bad there’s no
@mediatype'screenshot'so that we could change the formatting to show the absolute timestamp automatically upon taking a screenshot. (Then again, it would probably be too exploitable anyway…) Especially for apps, I’m liking my “add a dedicated screenshot function that reformats automatically” idea more and more.