News for hackers. Stuff that matters.

A comment on Technical Feasibility of Building Hitchhiker's Guide to the Galaxy. Parent comment

Re:Technical Feasibility of Building Hitchhiker's Guide to t... by ctdonath on Tuesday April 01, 2014 @10:00AM (#7508203)
One post on Twitter: 140 bytes max. One HD frame on Netflix: 6220800 bytes max.

If throwing the near-totality of human cinematography on H2G2 is a no-brainer due to its manageably small size (a mere 24TB), then may as well throw Twitter on there as well.

[ Parent | on HN ]
Re:Technical Feasibility of Building Hitchhiker's Guide to t... by pyre on Tuesday April 01, 2014 @06:03PM (#7512047)
It's probably easier to index and search Netflix than it is to index and search all of Twitter on a small device.
[ Parent | on HN ]
Re:Technical Feasibility of Building Hitchhiker's Guide to t... by misnome on Tuesday April 01, 2014 @10:11AM (#7508270)
Don't forget Unicode. 140 Characters =/= 140 bytes.
[ Parent | on HN ]
Re:Technical Feasibility of Building Hitchhiker's Guide to t... by ctdonath on Tuesday April 01, 2014 @11:05AM (#7508741)
Don't forget compression too. And don't forget most tweets don't use close to the full available tweet data space. A billion tweets takes up a lot less than 140GB.

I'm just looking at rough comparisons. A single 1/24th of a second of Netflix video approximates 44,000 tweets' worth of data. Anticipating growth, let's assume a billion tweets per day (was half-billion last October). 171 days of tweets takes up the same space as the complete Netflix library.

[ Parent | on HN ]