What they really need to do is express why this exists and what kinds of things it is good for. Even just a subset ("It can do much more, but these are the things that are already implemented") would be good.
I mean, I'm aware of #Beaker-Browser, but what else does it do? To some degree, this conference should have started with the idea that at least some of the attendees have no real background with #Dat / Hyper, #Beaker, or anything related.
If someone were to set up a #RasPi to be a node on one of these types of #peer-to-peer networks, would they need to set up NAT passthrough, or do their protocols already include something like STUN / TURN?
Mostly an academic question, as I’m not willing to potentially open up access to my home network.
I wonder if ipfs will be put back into Beaker, now that it seems ipfs people have decided on an `fs:` scheme as an interop prefix with things that insist on URIs.