Show HN: Hearth – A Dropbox-like, IPFS-powered personal website publisher
Never having used or looked into Beaker, dat, ipfs, etc, some immediate questions about security implications come to mind:<p>1) Someone accesses your &quot;site&quot; directly on your computer via ipfs&#x2F;dat whatever it is.  This is static content I guess?  And it&#x27;s like your computer is just running a static webserver (kinda&#x2F;sorta? if not, or something more dynamic please advise).  So, are there security implications here?  Is there an attack surface that a client&#x2F;viewer of your content could leverage?<p>2) Sort of opposite question as in 1.  You are the client&#x2F;viewer of the &quot;site,&quot; directly connected to some dude&#x27;s computer via ipfs&#x2F;dat or whatever.  Obviously I should use standard security measures and not just go clickity on anything&#x2F;everything I see, but beyond that, are there any other security implications for the client?  I could download a virus I&#x27;m sure by clicking or downloading a malicious file, but beyond that, could I get hacked by the target in a more dynamic way than that?<p>3) How do I &quot;navigate&quot; in ipfs&#x2F;dat-land?  How do I know what URL to go to, and if this &quot;URL&quot; might be a safe site, or like what the hell is this URL if it&#x27;s just some kind of hash?  Is there a &quot;google&quot; of ipfs&#x2F;dat sites&#x2F;content?<p>Stuff like this. :) Any feedback would be muchly appreciated!