71–80 of 160 posts
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)
Interestingly, there's a frame or two at the very beginning that shows a document open that could suggest an exploit of some kind. Screenshot: https://i.imgur.com/3oTXTDK.png
From: Pi To: Pi Subject: Project Time Machine - Test #3 It sounds like someone's trying to create some fun meta-fiction - it looks like a letter from the creator's future self to his past-self, describing future-self's experience going through some iteration of the time-loop ("Don't talk about fate. You did it once and it was cringy.")
Earlier quoted context omitted.
Excellent, this explains it. The YouTube video you shared says the trick is to create a resumable upload using YouTube API. The steps involved : 1. create a resumable session (here we specify video length in bytes) 2. YouTube returns a session URI which contains the upload ID 3. create a video with the upload ID baked in (edit video to match length from step 1) 4. upload video to the session URI https://developers.go…
I have not been doing any edits of video for a long time... What are most people editing vids with these days?
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)
This tweet (or one like it) caused a massive Twitter outage.
Earlier quoted context omitted.
Excellent, this explains it. The YouTube video you shared says the trick is to create a resumable upload using YouTube API. The steps involved : 1. create a resumable session (here we specify video length in bytes) 2. YouTube returns a session URI which contains the upload ID 3. create a video with the upload ID baked in (edit video to match length from step 1) 4. upload video to the session URI https://developers.go…
I have not been doing any edits of video for a long time... What are most people editing vids with these days?
Earlier quoted context omitted.
Excellent, this explains it. The YouTube video you shared says the trick is to create a resumable upload using YouTube API. The steps involved : 1. create a resumable session (here we specify video length in bytes) 2. YouTube returns a session URI which contains the upload ID 3. create a video with the upload ID baked in (edit video to match length from step 1) 4. upload video to the session URI https://developers.go…
I have not been doing any edits of video for a long time... What are most people editing vids with these days?
It would be more useful if Google / Youtube's API allowed 'reserving a slot' which would create a video ID endpoint but not finalize the content. Accounts might have a per-account limit of some small number of floating slots which would also timeout after a day or two. This wouldn't violate the write-once model since the submission wouldn't be completed, it'd just defer finalizing and publishing it for a little.
More useful for what application? Other than a novelty, why would anyone need a reserved spot?
It would be more useful if Google / Youtube's API allowed 'reserving a slot' which would create a video ID endpoint but not finalize the content. Accounts might have a per-account limit of some small number of floating slots which would also timeout after a day or two. This wouldn't violate the write-once model since the submission wouldn't be completed, it'd just defer finalizing and publishing it for a little.
More useful for what application? Other than a novelty, why would anyone need a reserved spot?
I think it's most likely done with the API. From what I remember from looking at it a while ago you can create the entry before, then it'll give you the right endpoint where you post your actual file to later on in the process. You just have to do that quickly enough so the endpoint doesn't expire.
It's apparently even been done before, see here at around the three minute mark: https://youtube.com/watch?v=UMYTSJTU0Vk