Join GitHub today
Outline the Various Applications of IPFS, with Use Cases and Dependencies #230
For each of the applications of ipfs that we've made issues for provide an outline of:
This was referenced
Mar 17, 2017
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.
referenced this issue
May 9, 2017
While similar to #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.
App store service
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…
On May 10, 2017, at 12:38 AM, Mikael Emtinger ***@***.***> wrote: 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... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#230 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHRavo4op7ySY78Wq-tjWaTKD9uu0e1Qks5r4JaXgaJpZM4MgFh8>.