Tincan isn’t meant to be a browser. The goal is to encourage everyone to have their own place on the Web (own domain + hosting) in an interoperable system that’s also stupidly simple to sign up for (all without making Small Technology Foundation a new centre). Getting there is going to require not just lines of code but also partnerships with likeminded hosts and domain registrars, etc.
My goal, however, is that you should be able to use Tincan with a standard browser. Would be great to think of what we could layer on top in a Dat-aware browser like Beaker but I’m nowhere near having the time to think about that yet.
Right now, I’m working on solving the seamless deployment issue and that means I’m still working heavily on Site.js (https://sitejs.org) while I wait for some stability around multiwriter (although it might be worthwhile to bite the bullet and go with something like peer-fs if that’s not a priority at the moment… I just want to remain compatible with mainline dat if possible… anyway…)
Hope that gives you some clarity (or at least that it hasn’t confused you further)
PS. If you want to get a feel for Site.js (what Tincan will be built on top of), check out the tutorial I released over the weekend for creating a basic chat app with it (doesn’t use Dat, just basic WebSockets):