Closed Aprillion closed 3 months ago
hm, what about the case where someone makes a minor typo fix on an outdated question and refreshes the date?
There has been effort to remove things from existing answers that might have a temporal context. Here is a link to the relevant meta-editing comment.
I think it has also been mentioned in the editing guidelines.
Do you think if the author just mentions the write date for time sensitive content in the answer it might mitigate the issue?
Another idea to address the problem that @plexish mentioned is to only update the last updated date when the amount of content changed is over some threshold. E.g num of text tokens changed in the doc. This requires a lot more doing as compared to the gdoc or the coda timestamp though.
how about something like the date when the question last changed status? That would handle most cases, i.e. from in progress to live on site seems like a decent cutoff. How often do live questions get major overhauls? Does their status get changed then?
weakly against trying to track this in the UI as it'll either be quite manual or miss many cases, and in favour of having a time-sensitive tag which the editors review regularly instead. status change is the best of a bad bunch of options, but i still don't love it
Whether this was good or not, this was completed, see https://github.com/StampyAI/stampy-ui/issues/381
I was checking a random page https://aisafety.info/?state=8368_ and realized that a lot of answers can be time sensitive / based on current news.
It would be useful to display a timestamp at the bottom of each answer, e.g. "Last updated: ..." - ideally based on the last edit of the Google Doc, but if that won't be possible, then it the time of last ingestion from GDocs to Coda should be good enough.