In only 9 days from today, on precisely Thursday July 13, 2017 10:39:59 PM
The Unix timestamps for filenames on 4chan will reach
>1499999999999
>1500000000000
Such an event only occurs once every 3 years. Who will be the lucky anons to GET these timestamps?
What are you planning on uploading to be immortalized in the GET hall of fame?
>>1436378
It's just a number bro
Have there ever been filename GETs in the past? It's next to impossible to predict the last three digits of a filename.
>>1436382
>It's just a number bro
it will be me
>>1436385
>>It's just a number bro
Feels like yesterday it broke into 140 or 130. How long does that second digit last, anyway? Two and a half years?
>>1436378
What do you mean? Any person can get those timestamps you only got to upload an image at that exact time then download it.
PSA needs more visibility
closer to death
oh boy
>>1437044
You know 4chan isn't a magic black box right? It's an actual server that has to process each individual image.
and even in the very remote chance that 2 people would end up with the same timestamp 4chan has ways of dealing with it to give one a different timestamp.
Also if you wait until that exact moment to upload you're definitely not going to get the right timestamp.
4chan's server code doesn't even begin processing your request until the entire image has been uploaded, so you have to begin uploading slightly before the exact time you want.
Honestly I wouldn't be surprised in the slightest if not a single anon got those timestamps, even if everyone were trying.
It's a long shot, which is what makes it even more amazing of a get then post numbers in my opinion.
>>1436382
GET THE FUCK OUT
>>1437010
Looks like about 3 years and 2 months.
>>1437711
>and even in the very remote chance that 2 people would end up with the same timestamp 4chan has ways of dealing with it to give one a different timestamp.
This happens frequently in fast sticky threads, its the reason you get two of the same image and everyone starts screaming MOOT since they were posted at the same time. They both receive the same timestamp.
>>1436385
this
>>1437939
I know that used to happen, but I thought they fixed it.
>>1436378
Neat.
>>1438994
What makes you think those are random numbers and not milliseconds?
>>1438994
At the very least, we should look for the closest timestamp.
>>1438996
Because unix time is only down to the second and tracking milliseconds sounds like it'd take resources unnecessarily.
>>1438999
Giving the Unix time in milliseconds is not uncommon. For example, open your Javascript console and type Date.now(); you will get the time in milliseconds.
Found the relevant part of the old 4chan source leak:
// time
$time = time();
$tim = $time.substr(microtime(),2,3);
microtime() gives the time in microseconds, and it does some string manipulation on that to get the milliseconds part.
http://php.net/manual/en/function.microtime.php
http://php.net/manual/en/function.substr.php
In the archives, you can search by time, so that might help finding the closest. I'll write some scripts anyway.
>>1439645
Yeah, I mean even if someone doesn't actually get either of those numbers it's still an historic occasion.
Because another way to look at it is that in a few days there will be the last image ever posted on 4chan from the 14* era and a first ever image of the new 15* era.
Here's my script:
https://pastebin.com/iQYjEA6j
>>1440024
looking for script kiddies wrong generation fuk boi
>fuck boy your the 10 ear pump