$5 Mt. Gox price contest! 2BTC

[kgo]

2012-JAN-25

[1713506289]

1713506289

[1713506289]

1713506289

[1713506289]

1713506289

[tvbcof]

###guess123###  1330224457  tvbcof

[tvbcof]

###guess123###  1330224457  tvbcof

Just FYI, I used the format above so that a quick list might be generated as so (for those on UNIX or MAC or with presumably cygwin on Windows.)

==========

wget --no-check-certificate -qO- "https://bitcointalk.org/index.php?topic=55275.0;all" | grep '###guess123###' | sed 's/&nbsp;//g' | sed 's/<br/ /g' | awk -F "###guess123###" '{print $2}' | awk '{print $1" "$2}' | sort -n | uniq

1330224457 tvbcof

==========

It's a bit of a hack and I would clean up the regular expressions and stuff if I was going to use it.

[netrin]

Perhaps Parimutuel betting, weighted by bet time before the event. That way multiple people place a wager on the same dates, increasing the winning pool to the advantage of the earlier betters.

ISO isn't difficult for both humans and computers to parse. I should think the following would suffice:

netrin: 2011-12-31

[tvbcof]

If I were running a game (and thus, the God of it) I would:

1)  Demand a tagged format such as I used above which would allow me, and probably about half of everyone else, to get a quick list of sorted results without wading through page after page on the forum, and

2) Demand UNIX time be used since it is widely understood, completely unambiguous, and easy for anyone to obtain for whatever timezone they like using something like this:

  http://www.epochconverter.com/

The winner would be chosen as a result of the most simple of arithmetic.  Period.  The chances of a tie (equidistant bets on either side) are so remote that I would happily pay each party in full if it happened.

I usually budget several hours of tearing my hair out whenever I have to do any time related coding.  Unix time makes most things vastly easier.

With some fiddling around, I could extend my hack above to automatically produce a human readable form from the stamp (but then questions arise about whether one is on BSD or Linux or has python installed (and where) and all that jazz...)

But I have no intention of running a game since I find them silly and only quasi-participated in this one as an experiment in various things.

[the joint]

If I were running a game (and thus, the God of it) I would:

1)  Demand a tagged format such as I used above which would allow me, and probably about half of everyone else, to get a quick list of sorted results without wading through page after page on the forum, and

2) Demand UNIX time be used since it is widely understood, completely unambiguous, and easy for anyone to obtain for whatever timezone they like using something like this:

  http://www.epochconverter.com/

The winner would be chosen as a result of the most simple of arithmetic.  Period.  The chances of a tie (equidistant bets on either side) are so remote that I would happily pay each party in full if it happened.

I usually budget several hours of tearing my hair out whenever I have to do any time related coding.  Unix time makes most things vastly easier.

With some fiddling around, I could extend my hack above to automatically produce a human readable form from the stamp (but then questions arise about whether one is on BSD or Linux or has python installed (and where) and all that jazz...)

But I have no intention of running a game since I find them silly and only quasi-participated in this one as an experiment in various things.

Now there's UNIX time?!  AHHHHHHHHHHHHHHHH

[btc_artist]

January 17th, 2012.

[btc_artist]

January 17th, 2012.

Actually, that's already taken, so I'll go with January 27, 2012.

[adamstgBit]

Jan 5th, 2012

[Jeremy West spendbitcoins.com]

See rule in OP:

Also the guessing needs to be for a future date, not past

Oh, man, he added that AFTER I made my prediction.

Oh well, I guess that was covered in this rule:

Disclaimer, as OP I am God and I can do whatever the fuck I want.

[the joint]

See rule in OP:

Also the guessing needs to be for a future date, not past

Oh, man, he added that AFTER I made my prediction.

Oh well, I guess that was covered in this rule:

Disclaimer, as OP I am God and I can do whatever the fuck I want.

Yup, I like your thinking but clearly I can't payout for that:)

And so it continues.

[bitclown]

2012-01-12 04:45:10.028 GMT

This is rejected as you failed on the timezone rule. Please try again.

Thanks, but I've decided to settle on Lunar Time for now.

[plastic.elastic]

AFAIK,
1/2/2012 is the 2nd of January, but
1.2.2012 is the 1st of February.
Can you bring an example of a country, where 1/2/2012 means the 1st of February?

Kid, what the fck did you do at school?

[notme]

AFAIK,
1/2/2012 is the 2nd of January, but
1.2.2012 is the 1st of February.
Can you bring an example of a country, where 1/2/2012 means the 1st of February?

Kid, what the fck did you do at school?

He went to a school where they teach different things than at your school.  It happens.  In some places is day/month/year, others it is month/day/year.  AFAIK if it's dots it is always day.month.year, but I wouldn't be surprised to find yet another date format used in the wild.

[Tril]

Nobody picked tomorrow yet? 
2011-12-23

[mc_lovin]

♥-DAY!

(Feb. 14, 2011)

[byronbb]

1st minute of Jan 3rd 2012.

[S3052]

it takes about 200 $k to hit 5 $ at the moment. There are enough funds on MtGox already. If people decide to have fun holiday trading,and have BTC before masses add funds to MtGox in the new year, we may hit 5 $ soon:

Guess: Dec 29, 2011

[netrin]

AFAIK,
1/2/2012 is the 2nd of January, but
1.2.2012 is the 1st of February.
Can you bring an example of a country, where 1/2/2012 means the 1st of February?

1/2/2012 is 2 January in the United States and 1 February in Europe, Latin America, Middle East, though everyone should be confused.

1.2.2012 would be 1 February most everywhere, though North Americans might be confused.

I have never come across mm.dd.yyyy anywhere in the world. Generally it is only the United States (and its minor influence in Philippines, Saudi Arabia, and Canada) that uses a dyslexic (mixed endian) system, where the /-slash is near universally used.

Europe, Mid East, Latin America and some of Asia use little endian, with just about any delimiter (., /, -, 年, 月) though big endian is more common in Asia. Only a four digit year would clarify the order.

I've seen some mixed delimiters, such as 22/12-2011, in Germany and nordic countries, or roman numeral months in central Europe, but it is always little endian, unless the delimiter glyph represent the month, year, such as in Chinese 2011年12月22日.

Generally, the / is completely ambiguous and should be avoided. Both . and - denote little endian or big endian and should contain a four digit year. I personally suggest big endian, four digit year, and abbreviated month for least ambiguity and maximum clarity, such as 2011-DEC-22.

[thegato]

I think DEC-27-2011