You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 30, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 30, 2026. It is now read-only.
Outline the Various Applications of IPFS, with Use Cases and Dependencies #40
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.
Reacted by Björn Roberg, Dmitriy Ryajov, Adam Lawrence, Wouter Scherphof, Masahiro Saito, Matej yangwao, David Vasandani, swanthropos, Anirudh Vyas and Alfonso Montero López
Reacted by FingerLiu, David Vasandani and swanthropos
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)
Here's a little demo of one implementation of a "decentralized YouTube" that uses IPFS for media storage/distrib (although we are not yet capturing views, geo data et cetera)
https://alexandria.io/browser/002004
On May 9, 2017, at 10:43 PM, Mikael Emtinger ***@***.***> wrote:
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)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
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...
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.
Reacted by Whyrusleeping, Michael Muré and Dmitriy Ryajov
Yes, that's the plan, and then supplement that with other non server-focused stats that can help gauge the relative popularity of a piece of content like size of swarm and total revenue collected for it to date
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
Activity
empaempa commentedon 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 commentedon May 9, 2017
empaempa commentedon 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 commentedon 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
App store service
DevonJames commentedon May 9, 2017
whyrusleeping commentedon May 10, 2017
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 commentedon Aug 12, 2018
@DevonJames got an updated link?
jessicaschilling commentedon Mar 26, 2020
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.