I actually tried this a while ago, and found that the audience also had to use Beaker to access the content. That's a huge barrier if current browsers don't support this.
One must start somewhere. You can use DatHTTPD [0] to mirror your site on HTTPS. There's also additional tools available on the project website [1].
They're also writing specs and working on adding support to Brave [2], or so says the third footnote on that article. Brave also has ongoing work to support IPFS [3].
Long-term, I'm hoping browsers will improve support for registering new protocols through extensions.
True but i think that their plan is to get into web standards and have IPFS and DAT in other browsers. Beaker is just first implementation. I believe Firefox people are already doing some work on those protocols.
It will be interesting see Googles position on those protocols. Chrome might be huge weapon against those iniciatives. Google can simply kill the whole initiative if they won't support it.
Beaker uses Dat protocol as opposed to HTTP under the hood. Dat protocol support is coming to Brave browser, probably Firefox next. The P2P web is about to take off.
