What does the OP have against “Google Drive” when seeking file storage via a Google Service?
Horses for courses… this is how we end up with pictures clogging transaction ledgers
YouTubeDrive: Store files as YouTube videos
211–220 of 316 posts
Re: YouTubeDrive: Store files as YouTube videos
#212I think my favorite part of this is that the example video linked to this has ads on it. It's a backup system that pays you. Well, until someone at Youtube sees it and decides to delete your whole account.
Re: YouTubeDrive: Store files as YouTube videos
#213The code looks not too big (a single file). But it requries a paid symbolic language (Mathematica) to be used. Anyone with better Mathematica knowledge explain if it can be ported to another symbolic (Sage, Maxima) or non-symbolic languages (R, Julia, Python)
Re: YouTubeDrive: Store files as YouTube videos
#214-Back in the day when file sharing was new, I won two rounds of beer from my friends in university - the first after I tried what I dubbed hardcore backups (Tarred, gzipped and pgp'd an archive, slapped an avi header on it, renamed it britney_uncensored_sex_tape[XXX].avi or something similar, then shared it on WinMX assuming that as hard drive space was free and teenage boys were teenage boys, at least some of those…
Poor guys, still looking for the right codec to play the britney tape they downloaded 28 years ago.
Disturbing, she'd have been 12 at that time.
Re: YouTubeDrive: Store files as YouTube videos
#215Re: YouTubeDrive: Store files as YouTube videos
#216Re: YouTubeDrive: Store files as YouTube videos
#217Earlier quoted context omitted.
I'm still confused on how this worked, did you email some address and get a reply with the attachment ?
Since GP says it was a POP3 server, I suppose you would set up an email account in your client with its inbox server pointing to that POP3 server. When the client requests the content of the inbox, the server responds with a list of "emails" that are really just files with some email header slapped on; so your email client's inbox window essentially becomes a file browser.
Yeah, that's basically it.
Re: YouTubeDrive: Store files as YouTube videos
#218Before broadband was widely available, TiVo used to purchase overnight paid programming slots across the US and broadcast modified PDF417 video streams that provided weekly program guide data for TiVo users. There's a sample of it on YouTube https://www.youtube.com/watch?v=VfUgT2YoPzI but they usually wrapped a 60-second commercial before and after the 28-minute broadcast of data. There was enough error correction in the data streams to allow proper processing even with less-than-perfect analog television reception.
Re: YouTubeDrive: Store files as YouTube videos
#219Earlier quoted context omitted.
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 used this as a backup target for the longest time. Simply split the backup file into 10 MB chunks and send as mails to a gmail account. Encrypted so no privacy problems. Rock solid for years. And as it was just storing emails it was even using gmail for it's intended purpose so no TOS problems..
[deleted]
Re: YouTubeDrive: Store files as YouTube videos
#220Earlier quoted context omitted.
This brings up an interesting question: what is the upper-bound of hidden data density using video steganography? E.g. how much extra data can you add before noticeable degradation? It's interesting because it requires both a detailed understanding of video encoding and also understanding of human perception of video.
I'd expect you could store more data steganographically than the raw video data. You can probably do things like add frames that can't be decoded and so are skipped by a decoder; that effectively allows arbitrary added hidden data. That's maybe cheating. If you stipulate that you can't already have a copy of the unaltered file, and the data has to be extractable from a pixel copy of the rendered frames ... that becom…
Youtube doesn't give you the raw video back, it does transcoding to their given standard bitrates/resolution sets.
You'll notice this if someone has just uploaded a video to Youtube and the only version available for playback is some 360p/480p version for a few hours until Youtube gets around to processing higher bitrates.
So whatever you're encoding has to survive that transcode process.