Live data from Hacker News

YouTubeDrive: Store files as YouTube videos

github.com

301–310 of 316 posts

Re: YouTubeDrive: Store files as YouTube videos

#301
Yes we have all done or used something similar when we were younger, but really, should this be on the front page of HN? This is abuse of a popular service and if it becomes popular it will only make YouTube worse and YouTube is getting worse without any additional help.

Re: YouTubeDrive: Store files as YouTube videos

#302

Earlier quoted context omitted.

No I'm pretty sure you're right on the timing. I was a teenager in the mid to late 90s and britney tapes were extremely common then, to the point that it was often used as a joke (much like in your story!)

WinMX was release 21 years ago, and Britney Spears definitely didn’t break out until around 1999 around the same time as Napster. The difference between 1994 and 1999 is quite a bit in show biz/pop culture and an absolutely huge difference in public uptake of the internet.

For the record, neither I nor the person I replied to said 1994 (unless they edited their post). I was thinking 97 or 98, so was still off, but at this point in my life being off by a year or two feels pretty damn close ;-)

Re: YouTubeDrive: Store files as YouTube videos

#304
post #161

Earlier quoted context omitted.

Yeah. Video, even old grainy VHS, had a pretty high bandwidth. Even much more so with S-VHS, which did not become super popular though. (I'm actually wondering whether the 2GB figure was for S-VHS, not VHS. Didn't to the math and wouldn't be surprised either way, though.)

A normal VHS encodes about 100 million scan lines over 2 hours. 20 bytes per scan line sounds feasible, since there's somewhere around 200-300 'pixels' of luma available in each scan line.

Thanks, that's a very reasonable back of the envelope calculation.

There are many fun details about VHS, its chroma resolution, and especially some weirdness around the PAL delay line, but they all don't really matter for this.

Wikipedia says there is about 3MHz of bandwidth, so ~200-300 "pixels" seems like a very good ballpark (just going by the fact that a normal PAL signal has about 6 MHz and is commonly digitized as 720x576, 3MHz about halves the horizontal resolution and taking some pixels off for various reasons makes sense).

Re: YouTubeDrive: Store files as YouTube videos

#305
post #59

Earlier quoted context omitted.

They still do if you pay for Prime. I was surprised to see that even RAW files (which are uncompressed and quite large) were uploaded and stored with no issues. Not the same as "hiding" data but might still be possible.

In the interest of technical correctness, RAW files are frequently compressed and even lossily compressed. For example, Sony's RAW compression was only lossy until very recent cameras. Given that there are the options for uncompressed, lossy compressed and lossless compressed, I'd say RAW files differ in the stage of the data processing where capture is being done and doesn't imply anything about the type of compress…

Interesting, so are you saying that the RAW signal coming from the hardware is already often compressed even before hitting the main software compression?

Re: YouTubeDrive: Store files as YouTube videos

#306

Earlier quoted context omitted.

In the interest of technical correctness, RAW files are frequently compressed and even lossily compressed. For example, Sony's RAW compression was only lossy until very recent cameras. Given that there are the options for uncompressed, lossy compressed and lossless compressed, I'd say RAW files differ in the stage of the data processing where capture is being done and doesn't imply anything about the type of compress…

Interesting, so are you saying that the RAW signal coming from the hardware is already often compressed even before hitting the main software compression?

Oh, no. What I'm saying is that cameras often take the raw signal from the hardware, but then the camera software frequently compresses that signal before writing it to a raw file (.cr2, .arw, .dng, whatever). This compression can be lossy or lossless. It's important not to confuse the raw signal with the RAW file (an actual format, often specific to the camera manufacturer). Just by saying RAW file, assuming it's lossless or uncompressed is false. So it should be specified - uncompressed RAW (lossless almost by definition), lossy compressed, lossless compressed.

Re: YouTubeDrive: Store files as YouTube videos

#307
post #279
post #231

Earlier quoted context omitted.

As if videos don't die...

well the point is the video and the file are linked - the video cannot exist without the file

This is a classic case of overengineering a solution to a nonexistent problem.

On YouTube, the video and the description are also linked. They exist on the same page always.

And even if the concern this solution is covering is what if the video is somehow shared without the description, away from YouTube, then the video could just as easily contain the description or URL or QR code pointing to the file.

This is a just horribly unusable QR code.

Re: YouTubeDrive: Store files as YouTube videos

#308
post #307
post #279

Earlier quoted context omitted.

well the point is the video and the file are linked - the video cannot exist without the file

This is a classic case of overengineering a solution to a nonexistent problem. On YouTube, the video and the description are also linked. They exist on the same page always. And even if the concern this solution is covering is what if the video is somehow shared without the description, away from YouTube, then the video could just as easily contain the description or URL or QR code pointing to the file. This is a jus…

The description is not big enough to hold practically any data. You would need to link to it from there.... at which point the two are no longer linked into existence. Links go down insanely often.

Re: YouTubeDrive: Store files as YouTube videos

#309
post #308
post #307

Earlier quoted context omitted.

This is a classic case of overengineering a solution to a nonexistent problem. On YouTube, the video and the description are also linked. They exist on the same page always. And even if the concern this solution is covering is what if the video is somehow shared without the description, away from YouTube, then the video could just as easily contain the description or URL or QR code pointing to the file. This is a jus…

The description is not big enough to hold practically any data. You would need to link to it from there.... at which point the two are no longer linked into existence. Links go down insanely often.

I'm not saying embed the file I the description. Add a URL that points to the asset like we've been doing forever... This solves nothing.

Re: YouTubeDrive: Store files as YouTube videos

#310
post #309
post #308

Earlier quoted context omitted.

The description is not big enough to hold practically any data. You would need to link to it from there.... at which point the two are no longer linked into existence. Links go down insanely often.

I'm not saying embed the file I the description. Add a URL that points to the asset like we've been doing forever... This solves nothing.

>add a URL that points

This works really well until it doesn't. I have seen so, so, so many videos have linked content in the description that links to sites which don't work anymore.

Post reply on HN