Sneakernet: 99% offline file sharing network
github.com
github.com
I've been rounding down here; the real bandwidth would be quite a bit higher.
http://www.sandisk.com/products/mobile-memory-products/sandi...
32GB Micro SD = 1 mm * 11 mm * 15 mm = ~6 million / m^3. So 32GB * 6,000,000 ~= 192 PB per m^3.
2TB 3.5 inch HDD = (4 in × 1 in × 5.75 in = ~3000 / m^3. So 3,000 * 2TB = ~6 PB per m^3
PS: Granted that m^3 if SD cards would cost around 1.2 billion and would take a while to upload at the other end.
What does the 3.5 inch figure represent, then? The size of the plates?
(3.5 * 69.9 / 102 = 2.3985)
But no, looked it up, 3.5" have platter sizes of 3.74" apparently, 5.25" had 5.12" platters. Which makes sense when you look at a hdd with the top off.
Not too long ago I had realized that my 1Gbps Ethernet network lets me have a higher sustain data throughput than my 5400 rpm laptop hard drive. You would have the same problem with the crate of hard drives depending how many times you have to copy the data...
Still, that's a shitload of bandwidth.
There was a software called "ourtunes" that would let you download things from these shares. It was amazing. People would name their libraries things like "room 204"...it had a great community feel to it :).
Also, my campus just shut down (or "officialized", take your pick) DC++.
The topper however is how almost 6 years later I was referred to and hired by a bio tech start up based on the fact that the CEO remembered me as the DC++ admin during his days in the dorms.
Nevertheless, good hack.
Installation instruction: 1. sudo gem install sneakernet 2. put your movie on a flashdrive and give it to your friend
Since you need to both write & read to transfer a file, you are looking at about 7MB/s file transfer which is about 50Mb/s (wireless order of magnitude).
Combined with the inconvenience, the benefits of this system are questionable.
I'd hazard a guess that the term was lifted from Navy or other such source far predating movement of electronic bits.
Anyone?
Audit trails are automatically generated, and can often be found on logs and cable trays.
It automatically logs everything! You'd also be able to identify people with broadband connections pretty easily.
So the goal of this is for the program to tell the person with files to load them up on a hard disk and then give them to the person requesting the files, who then picks them up from the dropbox, loads them on her computer, and then puts the flash drive back into the dropbox?
If so, then I guess all this really does is gives you a nice way of understanding who has which files, right?
If this is how it works, then I don't really understand what the external caches do for anyone.
The sneakernet is engineered basically to let you keep making trips to that cache outside your dorm room and somehow magical files appear from a block or two away. Also, files from you magically appear a block or two away when other people ask for them. The sneakernet takes care of all the routing to make lots of files show up in lots of places geographically close to you without too much overhead.
I've found lots of times I will request a file that the system in its cleverness has already cached locally on my HD. So "getting it off of the sneakernet" is actually instantaneous.
Huh? I thought that the point was that request files and then get them. How do you already have a file that you didn't request? Is this distributing files across people (i.e. FreeNet) so you have a bunch of files that are only on your machine for the purpose of being an intermediary to others? Or is this running some sort of predictive algorithm that tries to figure out what you will request before you do?
But, at the same time, you don't want a flash drive to be in a constant state of being near-full so it can't fit the new StarCraft beta.
So there's some logic that takes files that seem to be spreading around anyway and sort of spreads them around ahead of when they're requested. This both increases redundancy and increases network throughput. It's not exactly machine learning, but it does, in practice, provide decent results.
Also, by cache are you generally referring to some place where files are stored? Or does it mean something else?
I understand the system I just described doesn't really scale well, I'm just not really understanding how it does work from the documentation in the wiki.
Not through the internet. Through moving from flash drive to flash drive. If you follow the "testing" section along with the network maps for both the "basic configuration guide" and the "large configuration guide", that should clear up a lot of the magic.
You might want to say like storage device instead of cache, that would have made it less confusing for me to understand from reading the wiki.
It also seems like the system is just begging for caches to go missing (though I understand that as all the files are encrypted, it should be hard in theory to actually get data if you arent authorized access to sneakernet).
Are you hashing the files all the time to make sure that files aren't getting corrupted in transit or when taken from someones external cache?