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

Outline the Various Applications of IPFS, with Use Cases and Dependencies #40

Open
flyingzumwalt opened this issue Mar 17, 2017 · 8 comments

Comments

@flyingzumwalt
Copy link

For each of the applications of ipfs that we've made issues for provide an outline of:

  • use cases (very granular)
  • groupings of use cases (coarser, clearer)
  • which foundational features & functionality the use cases need or rely on (ie. libp2p, private networks, etc.) - this sources interdependence between feature sets
  • related products or projects that are addressing those use cases (ie. matrix working on p2p chat)
  • related organizations who either 1) have those use cases or 2) are building solutions for those use cases (ie. akasha, mediachain, openbazaar, neocities)

Guidelines:

  • Emphasize specific, deliverable user experiences - not just merged, not just a demo. Actual user experiences.
  • If a use case relies on an underlying library, link to the repo on github
  • If a use case relies on features or functionality that haven't been implemented or released yet, make sure there is a github issue in the appropriate repo for that feature and link to that issue from the use case.
@empaempa
Copy link

empaempa commented May 9, 2017

Would be interesting to outline how a YouTube would work - especially statistics such as number of views, geo data and other relevant data for publishers.

(In my mind, you should be able to put out any piece of content and be able to watch how it's being consumed)

@DevonJames
Copy link

DevonJames commented May 9, 2017 via email

@empaempa
Copy link

empaempa commented May 9, 2017

Nice! Is it possible to capture views/downloads "server side" so to speak (obviously possibly in the playback client). I haven't found anything in the API about this...

@Beanow
Copy link

Beanow commented May 9, 2017

While similar to ipfs/ipfs#246 Package Management. Software distribution in general is a prime candidate for IPFS I think. An IPFS based 3rd party Android store would be excellent. Or a good alternative to chrome apps. (See signalapp/Signal-Desktop#871 where secure code distribution is still unresolved) The main required properties would be simple to do.

Developers

  • Can publish APK files directly to IPFS as-is for the actual data.
  • Can use IPNS to update release info, app description, screenshots, etc. Which conveniently provides a form of code signing by extension.

App store service

  • Can provide a web app and native app using IPFS to navigate search indexes and app descriptions.
  • Can provide additional security by co-signing keys/releases (for example after a review process and/or automated malware scan), without having to duplicate any underlying data.
  • Can provide recovery procedures should developers lose the key to publish releases under.
  • Can seed relevant data and provide gateways.

@DevonJames
Copy link

DevonJames commented May 9, 2017 via email

@whyrusleeping
Copy link
Member

These are great conversations to have, Can we try to move them to a more specifically relevant issue? This thread will get quite large and hard to follow otherwise

@jaredatron
Copy link

@DevonJames got an updated link?

@jessicaschilling
Copy link

Note: Discussion on applications of IPFS are happening over in the IPFS Forums now ... please continue the discussion there!

This issue is being moved over to the archived repo https://github.com/ipfs/apps/ for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

7 participants