41–50 of 316 posts
Earlier 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?
something like this but far more mundane
Could 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.
Probably breaks TOS under video spam
Does YouTube store and stream all videos losslessly? How does this work otherwise?
Seems like a great way to get your account closed for abuse!
Does YouTube store and stream all videos losslessly? How does this work otherwise?
[1] https://www.cnet.com/tech/services-and-software/napster-hack...
Earlier 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?
Some forms of DRM are already essentially this, compression - and even crappy camera recording from a theater - resistant DRM that is essentially stegonagraphy (you can't visually tell its there) exist.
EDIT: "compression resistant watermark" is a good search phrase if anyone is curious
Could 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.
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"
I like to think you could unify all of these into a FUSE filesystem and just mount your transparent multi-cloud remote FS as usual.
It's inefficient, but free! So you can have as much space as you want. And it's potentially brittle, but free! So you can replicate/stripe the data across as many providers as you want.