markup.rocks
markup.rocks copied to clipboard
davidar
Replace Dropbox integration with IPFS
Instead of opening/saving files using Dropbox, we should use IPFS as the storage backend.
- IPFS Haskell API: ipfs/ipfs#4
CC: @osener @jamescarlyle @jbenet @diasdavid @bitemyapp @puffnfresh
@davidar what's the current state of hs-ipfs-api? I poked through it a few weeks ago, nothing looked particularly objectionable but I couldn't gauge where it was progress-wise.
State of the Haskell ecosystem
IPFS
Rating: Immature
@bitemyapp Sorry, I've been neglecting hs-ipfs-api (and I still need to address your PR :/ ), as I haven't really had much practical use for it yet (I'm waiting for IPLD to land). However, if people are interested in getting apps like markup.rocks integrated with IPFS, then it might be a kick in the pants to get the necessary functionality into hs-ipfs-api.
It looks like most of the dropbox-specific code is in static/jsbits.js. @diasdavid Would it be possible to make a drop-in replacement for IPFS?
Ideally, I'd like to be able to link to ...markup.rocks/#/ipfs/<hash-of-file-to-load> which would automatically open the specified file. When you saved the file, it would then update the hash in the URL bar to reference the current version. @osener Would that be difficult to do?
@davidar 'updatable' hashes are part of the IPNS spec, so it is totally doable :). To load an asset from IPFS on a URL hash (#/ipfs/..), you would have to have some JS code on your markup.rocks app that captures that hash and fetches the file for you, right now that can be done with node-ipfs-api
