131–140 of 160 posts
Earlier quoted context omitted.
What? 38 frames * 8 (or however many possible characters there are.
What? It's 62^11 * 0.016 (seconds). 11 because 11-character-long id; 62 because 62 possible characters in each location (26 lowercase, 26 uppercase, 10 numerals); 16ms in each frame of a 60fps video.
for idIndex in 0..Earlier quoted context omitted.
Okay, how did you do it?
Post first half, then edit? Just a guess.
Earlier quoted context omitted.
What? 38 frames * 8 (or however many possible characters there are.
What? It's 62^11 * 0.016 (seconds). 11 because 11-character-long id; 62 because 62 possible characters in each location (26 lowercase, 26 uppercase, 10 numerals); 16ms in each frame of a 60fps video.
YouTube uses base64 for the URLs, which makes 64 different characters
I divided it by 60 frames, 60 seconds, 60 minutes, 24 hours and 365 days
Earlier quoted context omitted.
The video, running at 60fps, would have to be 38996161157 years long for this to be a possibility Even if you predicted the first 3 symbols of the id, you'd still need a 148758 years long video
each possible digit, not each possible ID. You seem to be calculating some combinatorial explosion, where there probably is none
Reminds me of the guy that posted this: https://news.ycombinator.com/item?id=20456139
C.f. this tweet, which has a link to itself: https://twitter.com/mauritscorneIis/status/99142460340155187... (And as we all know Twitter has no edit button, no post-upload shenanigans are possible here, just some clever guessing and reverse-engineering Twitter's ID generation algorithm)
There's a decent write-up of how to do this here: https://www.spinellis.gr/blog/20090805/ As you said, it largely relies on reverse engineering and bruteforcing Twitter's ID generation.