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.

Sign up for GitHub

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

Jump to bottom

Explain how apps store data in IPFS #15

Open
flyingzumwalt opened this issue Feb 7, 2017 · 0 comments
Open

Explain how apps store data in IPFS #15

flyingzumwalt opened this issue Feb 7, 2017 · 0 comments
Labels
developers status/ready Ready to be worked topic/docs Topic docs
Milestone
Baseline for Brow...

Comments

@flyingzumwalt
Copy link
Contributor

Background

@Gozala:

It is somewhat unclear to me how would IPFS apps store content to IPFS, even if browser implemented ipfs specific protocol. I imagine that browser would have to expose some IPFS read / write operations as DOM APIs.

@jbenet:

  • For now, They can use js-ipfs to have a full ipfs node directly in the browser, or js-ipfs-api to use those APIs.

  • We want to come up with a nice set of APIs to be provided by {addon, extension, webextensions} that js-ipfs and js-ipfs-api can cleanly polyfill, so adoption can just improve over time.

  • Native APIs are the long-term goal.

  • Annother approach would only have the browser expose a libp2p Node (not a full IPFS node) and do all IPFS parts in js.

  • see https://github.com/ipfs/js-ipfs

  • see https://github.com/ipfs/js-ipfs-api
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
developers status/ready Ready to be worked topic/docs Topic docs
Projects
None yet
Milestone
Baseline for Browser Integration
Development

No branches or pull requests
2 participants
@flyingzumwalt @daviddias