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 &quot;experimental&quot; done by 3rd parties. <a href="https:&#x2F;&#x2F;flyingzumwalt.gitbooks.io&#x2F;decentralized-web-primer&#x2F;content&#x2F;avenues-for-access&#x2F;lessons&#x2F;tor-transport.html" rel="nofollow">https:&#x2F;&#x2F;flyingzumwalt.gitbooks.io&#x2F;decentralized-web-primer&#x2F;c...</a><p>3. Due to 1 and 2, any hosted content is EASILY trackable to a user&#x27;s computer, even behind NATs. A machine cryptokey also helps cement that (but can be changed). This allows easy DDoS&#x27;ing of any and all endpoints hosting content you don&#x27;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 &quot;sensitive&quot; 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.