3 ms·
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 s
by rebane2001 7y ago
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
- josinalvo 7y agoeach possible digit, not each possible ID. You seem to be calculating some combinatorial explosion, where there probably is none
- rebane2001 7y agoYou need to flash each possible ID, as the YouTube video editor only allows for trimming
- deleted 7y ago[deleted]
- TazeTSchnitzel 7y agoNo, YouTube lets you cut out parts of a video retroactively. “Video editor” might be the wrong name.
- megablast 7y agoWhat? 38 frames * 8 (or however many possible characters there are.
- earenndil 7y agoWhat? 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.
- ben_w 7y agoThat doesn’t seem to be what is being suggested. for idIndex in 0..<11 { for character in setOfPossible { draw(character) frame += 1 } }
- rebane2001 7y agoI calculated mine by doing 64^11/60/60/60/24/365 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