Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In-browser discovery of local-network IPFS nodes #45

Open
ghost opened this issue Feb 21, 2017 · 10 comments
Open

In-browser discovery of local-network IPFS nodes #45

ghost opened this issue Feb 21, 2017 · 10 comments
Labels
status/ready Ready to be worked topic/dependencies Topic dependencies ux

Comments

@ghost
Copy link

ghost commented Feb 21, 2017

FlyWeb provides mDNS-ish announcements and discovery in Firefox. This sounds ideal for WebRTC signaling. Instead of fixed signaling servers, ipfs in a browser tab can announce itself to the local network for signalling. @ipfs/javascript-team where's the caveat, this sounds too good to be true. 😍 And it would make for awesome browser demos. Here's how I cut my DSL cable, and Orbit still works.

My Firefox 51 here already seems to support it behind a feature flag.

@ghost ghost added the topic/dependencies Topic dependencies label Feb 21, 2017
@dignifiedquire
Copy link
Member

We would still need signaling servers for more global connections though, right? But this sounds very intersting if we can use it.

@ghost
Copy link
Author

ghost commented Feb 21, 2017

Yeah this would be for local/offline cases

@victorb
Copy link
Member

victorb commented Feb 21, 2017

Another discussion about FlyWeb: ipfs/js-ipfs#599

@ghost ghost mentioned this issue Feb 21, 2017
@ghost ghost added ux status/ready Ready to be worked labels Apr 18, 2017
@ghost
Copy link
Author

ghost commented Oct 8, 2017

Here's a few words from one of the FlyWeb devs on why it stalled:

16:29 | djvj | well, the maintenance stopped because there were some fires to put out generally in other parts of the codebase.
16:29 | djvj | Basically we came to the conclusion that the best way to push this forward was to go with a simple standalone mobile app (wrapping a WebView) that implements the FlyWeb client functionalithy.
16:29 | djvj | and then grow from there.
16:30 | djvj | But the whole quantum and Firefox desktop browser performance and QA effort came up right about then.
16:30 | djvj | So short answer: other priorities, not enough time to keep it running.
16:30 | djvj | pacer: if you want to do something with it, I'd be stoked.
16:31 | djvj | pacer: the apps (both iOS and Android) are available on our github.
16:31 | djvj | pacer: if you want to talk about what we had planned and why and what the general strategy was, that's cool too
16:32 | djvj | I still think it's a project with great promise, it's just that between work and new fatherhood, I don't have a lot of time to put towards this.

@lidel
Copy link
Member

lidel commented Jul 16, 2018

Multicast DNS API for browser extensions is being designed in mozilla/libdweb#7

@daviddias
Copy link
Member

That's excellent!! :D

@lidel
Copy link
Member

lidel commented Nov 5, 2018

@lidel
Copy link
Member

lidel commented Nov 5, 2018

Highly relevant:

@lidel
Copy link
Member

lidel commented May 8, 2019

@lidel
Copy link
Member

lidel commented Mar 22, 2020

Chrome 81 introduces the mobile web to NFC with an origin trial:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ready Ready to be worked topic/dependencies Topic dependencies ux
Projects
None yet
Development

No branches or pull requests

4 participants