You are reading content from Scuttlebutt

local webservers on firefox aurora

This looks promising - allows you to create web servers from inside the browser, accessible to the local network! and also uses mdns to discover available services.

That says firefox nightly, but the more up to date site
says it works on firefox aurora which you can install via google play. This could potentially mean that websbot could auto detect and do seamless local networking!

Looks like it's intended for opening a page hosted locally in the browser, and then communicating with that server. I wonder if it's possible for a long-running webapp to do local p2p via this? This might be enough to exchange webrtc introductions locally. Wondering if you can open a local webfly page in a iframe or something?

Liked this
Liked this in #scuttlebot
Liked this in #scuttlebot
Voted this

Since these are obviously not HTTPS, are they allowed to push out service workers?

Since you can only send mDNS (and not listen for it), you'd still need to do some kind of messaging between the flyweb page that the user just loaded and your actual webapp running under its real domain, if you want to use this for signaling.


Okay I tried this - I installed firefox-aurora on my laptop and phone, both where easy, and I enabled flyweb in about:config then it pretty much just worked.
I saw a flywebGP (the demo racing game) in the flyweb section, opened that on the phone - it opened a url like: http://468c6d34-f3a5-4f93-8a63-c7b501b5b9c7/ that is obviously unguessable. I wonder how long these persist?

Hmm, you could also have the flyweb service connect back to the regular app by opening the app in an iframe? However, at this point it would be just as easy to exchange webrtc introduction via QR codes.

I also tried (had to update a few things t get it to run, and it made sounds, but it didn't work)

Liked this in #scuttlebot
Liked this in #scuttlebot
Liked this in #scuttlebot
Voted this
Liked this in #scuttlebot
Liked this in #scuttlebot

I'd use Flyweb (with window.postMessage) just for handshakes. It takes the webRTC handshake from 2 per-connection identifiers to one per-session identifier, but no discovery API really sucks =/

The presentation API (coupled with a bootstrapper HTTPS page preloaded over app cache or service workers) might be another way to do both sides of offline browser peer introduction.

Join Scuttlebutt now