Design and evaluation of IPFS: a storage layer for the decentralized web
Lets remind everyone:<p>1. IPFS attaches ALL network interfaces (internal and external) to your identity.<p>2. Tor is still "experimental" done by 3rd parties. <a href="https://flyingzumwalt.gitbooks.io/decentralized-web-primer/content/avenues-for-access/lessons/tor-transport.html" rel="nofollow">https://flyingzumwalt.gitbooks.io/decentralized-web-primer/c...</a><p>3. Due to 1 and 2, any hosted content is EASILY trackable to a user's computer, even behind NATs. A machine cryptokey also helps cement that (but can be changed). This allows easy DDoS'ing of any and all endpoints hosting content you don't like.<p>4. It is trivial to ask the dHT for *who* has a certain content key, and get all (or the top 50?) computers hosting that content. (this matters with regards to "sensitive" content)<p>5. Running a node is still high cpu, ram, and network chattiness - so using a VPS to keep IPFS off your local network is still tenuous to run.