Autoclosing topics... Competition time again! - Results.
-
Continuing the discussion from Autoclosing topics... Competition time again!:
This topic was automatically closed after 2 days. New replies are no longer allowed.
Methodology from last time.
[pjh@lenovo ~]$ for x in `grep data-time /tmp/2825.html | tail -n10 | sed -e 's/^.*data-time="\([^"]*\)".*/\1/g' | cut -b1-10`; do date -ud @$x; done Mon Sep 1 14:35:49 UTC 2014 @Kuro Mon Sep 1 14:35:51 UTC 2014 @Matches Mon Sep 1 14:35:53 UTC 2014 @loopback0 Mon Sep 1 14:35:56 UTC 2014 @bp_ Mon Sep 1 14:35:57 UTC 2014 @dfk Mon Sep 1 14:35:59 UTC 2014 @VinDuv Mon Sep 1 14:35:59 UTC 2014 @anonymous234 Mon Sep 1 14:36:00 UTC 2014 @Luhmann Mon Sep 1 14:36:05 UTC 2014 @loopback0 Mon Sep 1 14:36:07 UTC 2014
[pjh@lenovo ~]$ for x in `grep data-time /tmp/2825.html | tail -n10 | sed -e 's/^.*data-time="\([^"]*\)".*/\1/g'`; do echo $x; done 1409582149430 1409582151546 1409582153901 1409582156014 1409582157980 1409582159122 @VinDuv 1409582159270 @anonymous234 1409582160314 1409582165475 1409582167987 @system
-
I think to make it fair, you should only count the replies with more than 15 words in them
Filed Under: totally random number and I totally did NOT count the amount of words in the replies after my last one!
-
Winner!
I hit the post button after the timer had gone, presumably the timer shows Discoseconds.
-
-
I assumed that even in Discoseconds, zero meant... well, zero.
Filed under: How can you get ZERO wrong?!
-
Romans had problems because they couldn't get the concept of zero right.
Filed Under: MMCCXIV
-
Winner!
I hit the post button after the timer had gone, presumably the timer shows Discoseconds.
In my case, the timer was off by around ~20 seconds. I think it uses the computer’s local time to do its calculations (at least for the remaining number of seconds) so it’s not very accurate.
It also seems that topics are effectively closed by a cron task; that would explain why you were able to post after the topic’s expected close time.
-
What's so great about 2214?
-
I did that last time, too based on what I was shown.
-
Oh, you'll find out (I'm about to summon it) </randomInternetReference>
As a matter of fact, I didn't even aim for any number close to ours. I just typed in random numbers hoping I would not get them confused (XC for example).
Filed Under: Should I take one X out to make it closer to todays year?
-
If you're going for 2014, it's MMXIV ;)
-
Not sure why I said "take one X out" because I can actually read roman numerals. But thanks anyway?
Filed Under: You just wait for 2214!! | 2204 is closer to 2014, though. So I was kinda right!
-
I didn't know either, I was confused so I was being modestly pedantic.
-
So I confused your pedanticness into modesty? Thats a strategy I should try to remember!
Filed Under: To confuse a pedantic dickweed, one has to either be very smart or very stupid!
-
No, I've been fighting off a serious tension headache that's trying to become a migraine.