@xkcd | 316,528 followers
I created a Google Calendar event in the year 7777 CE, but the start time in the confirmation email is off by an hour from the one in the calendar. I love imagining the heavy sigh from whoever handles this bug report.

Tweet Engagement Stats

Stats are based upon replies and quotes of this tweet

Engagement Map

Quotes
Replies
Retweets
Trendsmap

Replies and Quotes

Total of 56 replies and 14 quotes found
In reply to @xkcd
Nah, turns out in 5437 we get rid of daylight savings so it鈥檚 actually correct!
 
In reply to @xkcd
 
In reply to @xkcd
It's not an hour off from 7:07, it's ten minutes off from 7:77.
 
In reply to @xkcd
Second time in the last 15 minutes that I thank someone on Twitter for using CE. 馃檹 twitter.com/smurthys/statu鈥
 
In reply to @xkcd
At my last job, I submitted a PTO request for the week of the Unix epoch rollover.
 
 
In reply to @xkcd
I hope Stanley Rabinowitz ended up at Google, and the bug report lands on his desk. 1983 DEC Software Performance Report: sar.informatik.hu-berlin.de/teaching/2014-鈥 pic.twitter.com/KkMSQO8p8a
 
In reply to @xkcd
*heavy sigh* I work on how Google Calendar deals with time zones. The hour discrepancy is because the Google Calendar web client only knows about a limited number of DST transitions, so the client doesn't know that July is going to be in DST in the year 7777.
 
In reply to @xkcd
From the data back to 720 BC the fit gives an estimate for UT1-IAT of 1.329 days on 7777 AD. So, either we've kept up with the leap seconds, or you're on the wrong day. (from dx.doi.org/10.1098/rspa.2鈥 ) pic.twitter.com/1cUNIjoXlL
 
In reply to @xkcd
Maybe we can use that as, like, a bus stop for long-range time travel.
 
this is actually due to the convergence of daytime act in 6134 CE, not a bug
 
In reply to @xkcd
Are they time travellers or did immortality get figured out 馃槀 pic.twitter.com/Hjd4wxSSuo
 
In reply to @xkcd
I'd just mark it as resolved and hope to never hear from you again 馃槀
 
 
In reply to @xkcd
lol! You monster! 馃槀馃槀
 
 
In reply to @xkcd
That will be my sisters 7777th birthday. Should be a nice party
 
Le plaisir de trouver des bugs 茅tranges et inusit茅s.
 
The way we measure time totally makes sense, especially DST
 
 
In reply to @xkcd
Dude, what did Google Calendar ever do to you that you're willing to hurt it this badly?
 
Too many 7's it got fed up with them that's all
 
 
In reply to @xkcd
I think the key is that only 2 of the 7 invited guests have accepted. With 3 maybes and 2 not answering how can Randall plan for the event?
 
In reply to @xkcd
I guess it's an instant "Close - won't do". 馃槆
 
In reply to @xkcd
Try to sync that calendar to say outlook and see if anything crashes!
 
In reply to @xkcd
"Since the difference comparing now and the confirmation with now and the calendar is only 0.000001982412%, #wontfix." -Google, probably.
 
In reply to @xkcd
I imagining various expletives along with that sigh.
 
In reply to @xkcd
In the Jewish calendar, year 7777 is not *that* far.
 
In reply to @xkcd
Oh no! You are going to miss your meeting
 
 
馃槀馃槀馃槀馃槄
 
In reply to @xkcd
I guess nobody is going to see that, as either we've managed to eradicate ourselves, but maybe by that time there might be new archaeologists trying to figure out what happened to us...
 
In reply to @xkcd
Leap second issue?
 
In reply to @xkcd
I'm begging you, do not file that bug report
 
In reply to @xkcd
I guess the person will find it an nice report. Something out of order and refreshing while valid.
 
In reply to @xkcd
Every bug you get, is a gift. For many you will never notice, but drive you crazy! Cherish it!
 
In reply to @xkcd
Implying anyone at Google handles bug reports or support requests.
 
In reply to @xkcd
Try it across time zones!
 
In reply to @xkcd
I'm sure GPT Ultimum will be thrilled to deal with this bug, reported by other AIs interfacing in the system.
 
In reply to @xkcd
I have a dentist appointment scheduled for that day
 
 
In reply to @xkcd
Bugfix is scheduled for 7776.
 
 
In reply to @xkcd
This might be a feature. In Schr枚dinger terms, we cannot yet know if daylight savings will still exist.
 
In reply to @xkcd
 
In reply to @xkcd
Leap seconds ? Buit i think they are unpredictables en.wikipedia.org/wiki/Leap_seco鈥
 
In reply to @xkcd
That's all the leap seconds that will add up by that time.
 
In reply to @xkcd
sounds like a 2038 problem, but i dont think thats it鈥 2038 usually breaks things a lot more
 
In reply to @xkcd
send me an invitation
 
In reply to @xkcd
Yeah, and Sopwith Turtle is late. Again.
 
In reply to @xkcd
Could be a case for @jonskeet - or someone he knows :D
 
In reply to @xkcd
It knows that you will be in a different, neighboring time zone at that time.
 
In reply to @xkcd
Possible explanations: Daylight savings Timezone boundary changes Continental drift Leap hours A feature to never arrive 鈥榦n time鈥 for a party
 
In reply to @xkcd
Remember. Youre not giving them busywork. Youre creating jobs 馃槈
 
In reply to @xkcd
 
In reply to @xkcd
 
Users/Testers like these!!! :D
 
 
I want to come to the 7 party. it'll be my 5772nd birthday
 
In reply to @xkcd
Also the drift of the earth rotation and stuff so maybe it's adjusted for this as well
 
In reply to @xkcd
They have Jon Skeet, you know...
 
In reply to @xkcd
When you created it, was your system set to Central Time, perchance?
 
Over 7 replies and quotes not shown

Retweeters

No retweeters found
1,584 retweeters not shown
For access to this functionality a Trendsmap Explore subscription is required.

A Trendsmap Explore subscription provides full access to all available timeframes

Find out more

Thanks for trying our Trendsmap Pro demo.

For continued access, and to utliise the full functionality available, you'll need to subscribe to a Trendsmap Pro subscription.

Find out more

This account is already logged in to Trendsmap.
Your subscription allows access for one user. If you require access for more users, you can create additional subscriptions.
Please Contact us if you are interested in discussing discounts for 3+ users for your organisation, or have any other queries.