Add dat-polyfill

[RangerMauve]

Fritter is a great application for showing off the power of the P2P web.

That's why I think it would be a great starting point to get people onboarded from the regular web.

I've managed to get fritter to work on the web using dat-polyfill. From the look of it, pretty much everything is working.

• Creating new accounts
• Following users
• Viewing images / clicking links

Would you be open to having the dat-polyfill added into the main fritter repo? With that in place, people can view content from fritter on their phones, or on their desktops without having to install Beaker.

My goal with this is to give people a taste of what it's like and to make the technology more accessible. Ideally, people using the polyfill version of fritter should have something popping up prompting them to install Beaker (or Bunsen once that's out on mobile), along with a description of why it'd be better (privacy, offline-first, etc).

Some of the limitations of I can thing of when using this approach:

• Gateways can discover which dats a user is accessing, so users should be aware that they might have their dat URLs seen by third parties (my gateway doesn't track any of this, but it's a technical limitation)
• Currently there's just my gateway that's up which has this websocket sync thing, and it doesn't have TLS support yet.
  • I'll need to figure out getting letsencrypt wildcard certs up, or you'll need to set up a different one elsewhere. Maybe a reason for adding WS support to Hashbase
• My gateway doesn't support the 404 fallback yet so URLs on fritter won't work on it after refreshing
  • This won't matter too much since people will be accessing it through the hashbase version of fritter which works properly
• I don't have the versions of dat-polyfill or dat-archive-web that work tagged yet, but that'll be done soon.

[pfrazee]

I'd definitely be interested in seeing this! It's exactly the use-case that @flpvsk is asking about in beakerbrowser/beaker#1018

[RangerMauve]

Awesome. I think the only blocker would be to have a gateway with HTTPS that people can use. I'll send a PR when it's ready.

By the way, would you mind linking me to whatever you followed to get the Letsencrypt wildcard DNS cert working for hashbase? Do you have it automated by any chance?

[pfrazee]

I dont recall what I used, but I had to google around a bit. I maybe found it in an issue

[RangerMauve]

K, I'll just look around, then. I don't think the docker image is compatible with my DNS registrar, sadly. :(