Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

YouTubeDrive: Store files as YouTube videos

github.com

Post reply on HN
Print view View original

61–70 of 316 posts

Re: YouTubeDrive: Store files as YouTube videos

#61

Post by jasonlotito »

umvi wrote: post #26

Turns out any site that allows users to submit and retrieve data can be abused in the same way: - FacebookDrive: "Store files as base64 facebook posts" - TwitterDrive: "Store files as base64 tweets" - SoundCloudDrive: "Store files as mp3 audio" - WikipediaDrive: "Store files in wikipedia article histories"

My friends and I had a joke called NSABox. It would send data around using words that would attract the attention of the NSA, and you could submit a FOIA request to recover the data. I always found it amusing.

Re: YouTubeDrive: Store files as YouTube videos

#62

Post by xhrpost »

Not immediately obvious from the Readme, but does this rely on YT always saving a providing download of the original un-altered video file? If not, then it must be saving the data in a manner that is retrievable even after compression and re-encoding, which is very interesting.

Re: YouTubeDrive: Store files as YouTube videos

#63

Post by itake »

umvi wrote: post #26

Turns out any site that allows users to submit and retrieve data can be abused in the same way: - FacebookDrive: "Store files as base64 facebook posts" - TwitterDrive: "Store files as base64 tweets" - SoundCloudDrive: "Store files as mp3 audio" - WikipediaDrive: "Store files in wikipedia article histories"

Back in the day when @gmail was famous for their massive free storage for email, ppl wrote scripts to chunk large files and store them as email attachments.

Re: YouTubeDrive: Store files as YouTube videos

#64

Post by LewisVerstappen »

bityard wrote: post #53
LewisVerstappen wrote: post #21

Earlier quoted context omitted.

You'd be surprised how much YouTube lets you upload. I've been uploading 2-3 hours of content a day every day for the past few years. On the same account too. I have fewer than 10 subscribers lol.

What kind of content do you upload? (Should "content" be in air quotes? :P)

Lol yeah.

It's just recordings of myself when I'm doing deep work. I use OBS to stream my computer screen and a video recording of myself (mostly me muttering to myself).

It helps me avoid getting distracted (I feel like I'm being watched lol) and it's also interested to check back if I want to see what I was working on 3 months ago.

All the videos are unlisted or private.

Re: YouTubeDrive: Store files as YouTube videos

#65

Post by throwaway0a5e »

baud147258 wrote: post #12
throwaway0a5e wrote: post #6

Earlier quoted context omitted.

>Is it really abuse if the videos are viewable / playable? Presumably the ToS either already forbids covert channel encoding or soon will. If creators start encoding their source and material into their content Google would probably be fine with that because it gives them data but also gives them context for that data. Edit: I meant like "director's commentary" and "notes about production" type stuff like you used to…

> If creators start encoding their source material into their files Google would probably be fine with that it'd depends, as I don't think people using YT to store files would watch a lot of adds

If creators use it like the appendix in a book I can see people watching ads on their way to it.

Re: YouTubeDrive: Store files as YouTube videos

#67

Post by ihaveajob »

itake wrote: post #63
umvi wrote: post #26

Turns out any site that allows users to submit and retrieve data can be abused in the same way: - FacebookDrive: "Store files as base64 facebook posts" - TwitterDrive: "Store files as base64 tweets" - SoundCloudDrive: "Store files as mp3 audio" - WikipediaDrive: "Store files in wikipedia article histories"

Back in the day when @gmail was famous for their massive free storage for email, ppl wrote scripts to chunk large files and store them as email attachments.

I know someone who published an academic paper on doing exactly this.

Re: YouTubeDrive: Store files as YouTube videos

#68

Post by nittanymount »

LewisVerstappen wrote: post #64
bityard wrote: post #53

Earlier quoted context omitted.

What kind of content do you upload? (Should "content" be in air quotes? :P)

Lol yeah. It's just recordings of myself when I'm doing deep work. I use OBS to stream my computer screen and a video recording of myself (mostly me muttering to myself). It helps me avoid getting distracted (I feel like I'm being watched lol) and it's also interested to check back if I want to see what I was working on 3 months ago. All the videos are unlisted or private.

wow, curious, are you keeping these videos there, or will delete them after several months?

Re: YouTubeDrive: Store files as YouTube videos

#69

Post by havblue »

jasonlotito wrote: post #61
umvi wrote: post #26

Turns out any site that allows users to submit and retrieve data can be abused in the same way: - FacebookDrive: "Store files as base64 facebook posts" - TwitterDrive: "Store files as base64 tweets" - SoundCloudDrive: "Store files as mp3 audio" - WikipediaDrive: "Store files in wikipedia article histories"

My friends and I had a joke called NSABox. It would send data around using words that would attract the attention of the NSA, and you could submit a FOIA request to recover the data. I always found it amusing.

I've heard of the loic ion cannon dos tool described as a shortcut to getting sent to jail. This sounds similar.

Re: YouTubeDrive: Store files as YouTube videos

#70

Post by dotancohen »

bityard wrote: post #52
upupandup wrote: post #41

Earlier quoted context omitted.

Couldn't you also embed data through sound? Upload a video of a monkey at the zoo but you insert ultrasound with encoded data. something like this but far more mundane https://www.youtube.com/watch?v=yLNpy62jIFk

> but you insert ultrasound with encoded data Others in these comments have also suggested steganography in both the video and audio streams. The problem with that is that when you retrieve a video from YouTube, you never get the original version back. You only get a lossy re-encoded version, and the very definition of lossy encoding is to toss out details that humans can't (or wouldn't easily) perceive, including ul…

It might be ridiculous, but how about uploading a computer-generated video of a human saying 0 and 1 very quickly, to encode binary file.

Or better yet, the file could be one third the size if the human says the numbers 0 to 7.

Post reply on HN