UNIX conversion says that we'll hit 16 in 2020
Cool
>been here since 10
Does anyone know which image was the tipping point between 14 and 15
>>61384375
It was this one from /a/
Man I feel stupid now for not knowing that these filenames have been UNIX time all along...
>>61384443
mind=blown
>>61384443
Well, you'd never have got into cicada 3301 that's for sure
>>61384395
But that clearly has 114s at the end
>>61384517
It's the closest image to the timestamp
Nobody posted an image at the exact moment
>>61384517
The last three digits are randomly generated.
>>61384645
Thought they were server milliseconds or something?
>>61385219
Nope. Random.
I've been on 4chan since 1360
>>61385911
NEWFAG GET OUT
>>61382904
121* is my oldest image
>>61387038
Early 2008, and I'm still a newshit
oldest image i've got
>>61382904
How will 4chan deal with the 2038 problem?
>>61387572
There's no 2038 problem if 2038 doesn't exist.
>>61387594
2038 is a social construct.
>>61387506
loomis
>>61387572
Depends if it is still running 32bit or 64bit.
If it is 64bit then the filename strings will just become one character longer. Even if it is 32bit the strings might become one character longer, depending on what the servers are running on and how that software handles the roll over.
>>61382904
>>61387893
What image is 1500000000000 how can we check.
>>61387893
>If it is 64bit then the filename strings will just become one character longer
no they won't.
>>61387904
closest there is >>>/a/159778296
I found a collision yesterday on /b/.
thumb:https://thebarchive.com/data/b/thumb/1500/08/1500084594880s.jpg
both src:https://thebarchive.com/data/b/image/1500/08/1500084594880.png
https://thebarchive.com/data/b/image/1500/08/1500084594880.jpg
Why doesn't the image name works like the post number to avoid that?
>>61387059
heh, nice
>we will never 1488 again
>>61388293
Interesting
>>61388448
Fuck off /pol