Seems like a great way to get your account closed for abuse!
You could make it much harder to detect by synthesizing a unique video with a DNN and hiding the data using traditional stenography techniques.
YouTubeDrive: Store files as YouTube videos
31–40 of 316 posts
Re: YouTubeDrive: Store files as YouTube videos
#32Earlier 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.
Lucky you. I just posted my first two videos from a conference that were banned within a day for violating "Community Guidelines" without appeal.
[deleted]
Re: YouTubeDrive: Store files as YouTube videos
#33Seems like a great way to get your account closed for abuse!
You could make it much harder to detect by synthesizing a unique video with a DNN and hiding the data using traditional stenography techniques.
I think that video compression might make this not a viable technique. Artifacts would destroy the hidden data, right?
Re: YouTubeDrive: Store files as YouTube videos
#34Turns 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"
What a great time to write botnets
Re: YouTubeDrive: Store files as YouTube videos
#35Does YouTube store and stream all videos losslessly? How does this work otherwise?
things like redundancy and crc checks I assume
Re: YouTubeDrive: Store files as YouTube videos
#36Does YouTube store and stream all videos losslessly? How does this work otherwise?
The data is represented large enough on screen that compression doesn't destroy it.
Re: YouTubeDrive: Store files as YouTube videos
#37Does YouTube store and stream all videos losslessly? How does this work otherwise?
[deleted]
Re: YouTubeDrive: Store files as YouTube videos
#38Earlier quoted context omitted.
You could make it much harder to detect by synthesizing a unique video with a DNN and hiding the data using traditional stenography techniques.
I think that video compression might make this not a viable technique. Artifacts would destroy the hidden data, right?
That is what redundancy and error correcting codes are for. It will reduce your data density, but I am sure you can find parameters that preserve the data.
Re: YouTubeDrive: Store files as YouTube videos
#39Could youtube-dlp and YouTube Vanced now be hosted on.. YouTube? I wonder how long it'd take for Google to crack down on the system abuse. Is it really abuse if the videos are viewable / playable? Presumably the ToS either already forbids covert channel encoding or soon will.
>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
Not true at all, lol. Google has a paid file storage solution. YouTube is for streaming video and that's the activity they expect on that platform. I couldn't imagine any service designed for one format would "probably be fine" with users encoding other files inside of that format.
Re: YouTubeDrive: Store files as YouTube videos
#40Does YouTube store and stream all videos losslessly? How does this work otherwise?
No, YouTube is not lossless.
The video that is created in the example in the README is https://www.youtube.com/watch?v=Fmm1AeYmbNU
We can see that data is encoded as "pixels" that are quite large, being made up of many actual pixels in the video file. I see quite bad compression artifacts, yet I can clearly make out the pixels that would need to be clear to read the data. It looks like the video was uploaded at 720p (1280x720), but the data is encoded as a 64x36 "pixel" image of 8 distinct colors. So lots of room for lossy compression before it's unreadable.