News for hackers. Stuff that matters.
Re:Show HN: YouTube Filesystem – YTFS by bch on Monday July 06, 2015 @02:37PM (#9841218)
Unless what you were encoding wasn't meant to be consumed as a bytestream. If you encoded a resilient optical format (like UPC or QR codes), transcoding the format shouldn't be a deal breaker. Obviously it's not optimized for backing up a harddisk, though.

Edit: @ionforce hints at same here: https://news.ycombinator.com/item?id=9840838

Re:Show HN: YouTube Filesystem – YTFS by NeutronBoy on Monday July 06, 2015 @07:44PM (#9842822)
Interesting - say video @ 60fps, encode 1 QR code per frame, would be highly resistant against transcoding errors, very easy to extract information from again given the standard format.

Wouldn't be terribly efficient though. Wikipedia says max bytes per code is 2953 per QR code [1]. So 2953Bps * 60fps = 177KBps data encoding. I guess that's what you get for encoding it in a visual (human readable) format instead of a datastream directly.

[1] https://en.wikipedia.org/wiki/QR_code#Storage

Re:Show HN: YouTube Filesystem – YTFS by amino on Monday July 06, 2015 @09:42PM (#9843196)
you have sound too. Must be an audio equivalent that would have a similar level of durability to a qr code. I dont know if youtube ever drops frames during compression. Perhaps using there 4k support would help get a bit more data
Re:Show HN: YouTube Filesystem – YTFS by bch on Tuesday July 07, 2015 @12:25AM (#9843628)
You could reference this[0] vintage Commodore tech for ideas.

[0] https://en.wikipedia.org/wiki/Commodore_Datasette