>
1) Someone accesses your "site" directly on your computer via ipfs/dat whatever it is. This is static content I guess? And it's like your computer is just running a static webserver (kinda/sorta?It's like static content served by bittorrent. The content might be served directly by your computer, or by other nodes in the ipfs/dat network which are caching your content.
> So, are there security implications here? Is there an attack surface that a client/viewer of your content could leverage?
An attacker could try to exploit vulnerabilities in the IPFS/DAT network. This would be similar to exploiting vulnerabilities in bittorrent.
Or they could try to steal the private key used to publish your content, and publish malicious updates.
If access to your content is restricted (ie with a secret hash or url), an attacker might try to get access to it.
Overall the security model is quite straightforward, with a smaller attack surface than typical dynamic web stacks.
> 2) Sort of opposite question as in 1. You are the client/viewer of the "site," directly connected to some dude's computer via ipfs/dat or whatever. Obviously I should use standard security measures and not just go clickity on anything/everything I see, but beyond that, are there any other security implications for the client? I could download a virus I'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?
It's pretty much the same security model as regular web content, as you mention. The only exception might be a vulnerability in the ipfs/dat code, since your computer might be running a local node.
> 3) How do I "navigate" in ipfs/dat-land? How do I know what URL to go to, and if this "URL" might be a safe site, or like what the hell is this URL if it's just some kind of hash? Is there a "google" of ipfs/dat sites/content?
IPFS has a naming system called IPNS, where addresses are based on a unique crypto keypair. Addresses look like `/ipns/`. You can use specialized ipfs software, like the `ipfs` cli, or navigate your regular browser to an http gateway. For example, with the official gateway you can navigate to ``" rel="nofollow">https://ipfs.io/ipns/`. Ipfs also has a facility to easily alias a DNS domain to an ipns key, so you can navigate to `/ipns/`
Dat I believe has a similar system. The main difference is that, thanks to Beaker, you can bypass the gateway system - just navigate to `mydomain.com` and, if it's dat-enabled, the browser will lookup the corresponding key and fetch the content via dat instead of http.
There's no reason IPFS couldn't work the same way - you just need a browser to implement iofs support directly in the same way. Personally I hope Beaker will find the time to support both!
> Is there a "google" of ipfs/dat sites/content?
Not that I know of. But I think it's inevitable!