It seems ask.sagemath.org (or rather Askbot) has fallen prey to the Y2k20 bug, just in its date format. Just look at how the dates of some posts or comments are formatted: Previously they would be displayed like "Dec 31 '19" and now they display "Jan 7 '0" with the year formatted as "'0" instead of "'20".
I don't know if it's worth doing anything about; I just found it amusing.
This is due to a hilarious modification (in AskBot), made in 2012, to the jQuery timeago plugin:
return month_date + ' ' + "'" + date.getYear() % 20;
Yes, I'm sure that produced the right result in 2012. The same bug is still present in AskBot today.
An easy fix is to replace 20 by 100.
I do not know if this is fixed in recent versions of askbot. The issue is that migrating askbot is always a pain, since Django migration scripts (formerly "south") lead to errors that have to be fixed by hand, because the db of asksage was tweaked at install time by the askbot developer a very long time ago, so we try not do to it often :)
Note that it is only about js formatting : if you pass the mouse over the date without clicking, you see the whole date.
The fix has been merged in Askbot.
Ask LibreOffice also suffered from the bug. They deployed a version of Askbot with the fix.
Asked: 2020-01-07 16:16:27 +0100
Seen: 4,584 times
Last updated: Sep 13 '20
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
This could be reported to one or both of:
This ended up being reported at Ask Askbot
'0and on the Askbot issue tracker
and there is now a proposed fix
Thanks @Iguananaut and @rburing for the report and the analysis!