news:
there is BIG filename get happening tomorrow
ok that'ss it for the news
>>5578711
oh i have always been interested in these gets but no one else cared finally I have someone who is interested in them too can you please explain these gets to me well the main problem is the 4chan filenames are hidden now what a pain how annoying geeze that's super rude
>>5578711
someone would have to time it juuuuust right
>>5578717
Unix time is a system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970.
The get will occur July 13th, 2017 10:40 PM
prepare to kek like youve never kekeed before
>>5578721
>tfw off by one
>1500000000001
no one will notice any gets anyways because they're hidden
is that how the filenames work
i always thought it was a hash or something
>>5578733
good dubs
>>5578750
not even, heres the cool part, if two people post at the exact same moment one person's image gets overwritten and magic things happen
im wait
>>5578763
i've always wondered what happens if three people do
fugg I was hoping it would be possible to time an image upload perfectly to get the digits, but 4chan doesn't use the exact same number as >>5578723 for the timestamp, it adds four extra digits at the end that represent milliseconds
We could get 150000000XXXX with the Xs being random numbers but getting perfect zeroes is incredibly unlikely, unless tons of figs all attempt for the GET at once, its possible at least one lucky lad will hit it and we will check like we've never checked before
If we worked together we could maybe post enough images at once when the time comes and possibly get the digits, its more likely it will happen on /b/ tho
Your fortune: Reply hazy, try again
>>5578711
o boy!
WEW LAD
E
W
L
A
D
so what kind of image should it be?
>>5578711
Man, the 1.1Bs times were pretty good compared to now. 1.2B was when the world really went downhill. 1.3B and 1.4B have just been generally terrible. I hold no hopes for 1.5B.
>>5578763
That hasn't happened for a few years now, sadly.
>>5579309
I've seen it in the last year for sure
>>5579305
i'll agree
>>5579986
yo fellow page 10 surfer hows things
>>5579297
A Doremi pic
>>5578871
I will joining
bump4epic
6 hours away now holy wew
I'll be asleep when it happens
keep me posted
ill don geddit but gl ilu x
3 hours!!!!!!!!
2 hours bbys
let's check how close we are
>>5581288
>>5581288
wow dubs
we have to try and steal the big get, it needs to be VERY precise
the current time is 12:55am GMT
at 2:39:59am GMT, post a photo so that we might get 1500000000000
>>5581304
you don't have to steal it from anyone if you post on any board at the right time the image will have that timestamp
>>5581331
keep posting
1 hour away!!!
>At 02:40:00 UTC on Friday, 14 July 2017, the Unix time value will equal 1,500,000,000 seconds.
>At 03:33:20 UTC on Wednesday, 18 May 2033, the Unix time value will equal 2,000,000,000 seconds.
>At 06:28:16 UTC on Thursday, 7 February 2036, Network Time Protocol will loop over to the next epoch, as the 32-bit time stamp value used in NTP (unsigned, but based on 1 January 1900) will overflow. This date is close to the following date because the 136-year range of a 32-bit integer number of seconds is close to twice the 70-year offset between the two epochs.
>At 03:14:08 UTC on Tuesday, 19 January 2038, 32-bit versions of the Unix time stamp will cease to work, as it will overflow the largest value that can be held in a signed 32-bit number (7FFFFFFF16 or 2,147,483,647). Before this moment, software using 32-bit time stamps will need to adopt a new convention for time stamps, and file formats using 32-bit time stamps will need to be changed to support larger time stamps or a different epoch. If unchanged, the next second will be incorrectly interpreted as 20:45:52 Friday 13 December 1901 UTC.
>At 06:28:15 UTC on Sunday, 7 February 2106, the Unix time will reach FFFFFFFF16 or 4,294,967,295 seconds which, for systems that hold the time on 32-bit unsigned integers, is the maximum attainable. For these systems, the next second will be incorrectly interpreted as 00:00:00 Thursday 1 January 1970 UTC.
>At 15:30:08 UTC on Sunday, 4 December 292,277,026,596, 64-bit versions of the Unix time stamp would cease to work, as it will overflow the largest value that can be held in a signed 64-bit number. This is nearly 22 times the estimated current age of the universe, which is 1.37×1010 years (13.7 billion).
announcement: please to upgrade your computer before december 292,277,026,596
>>5581403
>please to upgrade your computer before december 292,277,026,596
FUCK that
oh god oh god oh god
did someone get it?
>>5582086
no one got it. but we were close
>>5581627
shit nigga it happened
>>5581403
>Sunday, 4 December 292,277,026,596
earth would probably be destroyed by ayyliums way before that
For the new era!
im lukin fir gold.....lol
>>5578711
literally poop
This is nice filename