Otherwise, you will need a dat:// client - Beaker is the main web browser with dat:// support, other clients sofar have more specialised uses, e.g. https://github.com/codeforscience/sciencefair
Otherwise, you will need a dat:// client - Beaker is the main web browser with dat:// support, other clients sofar have more specialised uses, e.g. https://github.com/codeforscience/sciencefair
Beaker/Hashbase dev here. Not quite, imo. The key difference is that a service like Hashbase has no special authorship priveleges (unlike Google Docs or Dropbox), and is instead an agnostic peer. We think that's an important distinction.
https://blog.mozilla.org/addons/2018/01/26/extensions-firefo...
Is there a first HN reference to a valid dat:// website already?
Not really. Need ways of bridging the gap.
The DAT network seems interesting and is new to me, but like you said, needing a central node to cache the data seems like breaking the p2p story.
The main benefit is that users of http browsers can visit your dat:// site.