IPFS Camp 2019
camp.ipfs.io
camp.ipfs.io
Sorry for such a rudimentary question. Literally just learned about IPFS this week.
IPFS PubSub Demo: https://www.youtube.com/watch?v=Nv_Teb--1zg
Google Docs esque clone with CDRTs: https://www.youtube.com/watch?v=-kdx8rJd8rQ
Theres also a pubsub room example on the ipfs-shipyard github: https://github.com/ipfs-shipyard/ipfs-pubsub-room
You'd use normal https://en.wikipedia.org/wiki/HTTP_Live_Streaming
And merely use IPFS urls for each file piece. Whether its that simple in practice...
E.g. so that ipfs://mydoma.in would "just work" with ipfs capable clients and I can update it easily.
It won't be ipfs://mydoma.in as the IPFS namespace is only content-address.
* 'Support for Decentralization Protocols' in https://blog.mozilla.org/addons/2018/01/26/extensions-firefo...
* https://addons.mozilla.org/en-US/firefox/addon/ipfs-companio...
Eg: ipns://dist.ipfs.io => http://localhost:8080/ipns/dist.ipfs.io
Firefox only as noted by devttyeu
There is talk of adding signed HTTP exchanges (same thing AMP uses to achieve the same idea[0]), but with content hosted on IPFS[1].
Native support for this may land in Brave someday currently there is an effort around adding IPFS[2]
[0] https://news.ycombinator.com/item?id=19678914
[1] https://github.com/ipfs/in-web-browsers/issues/121
[2] https://github.com/brave/brave-browser/issues/819#issuecomme...
It'll be in the format /ipns/mydoma.in