search

ipfs / apps

Coordinating writing apps on top of ipfs, and their concerns.
60 stars 9 forks source link

IIIF #26

Open davidar opened 8 years ago

davidar commented 8 years ago

Goal: automate the process of getting IIIF manifests and assets into IPFS

Related: #25

mekarpeles commented 8 years ago

Cool goal! @davidar also archive.org is trying to make a shim to enable any archive.org item to be accessed/served over IPFS. Perhaps this can be done in a way which gives us the IIIF use case for free as well. I'll talk to @edsilv and @aeschylus about this tomorrow

davidar commented 8 years ago

Possibly relevant:

Cc: @klokan

edsilv commented 8 years ago

Using TMS would require a shim - if it's a IIIF tile source, the URIs of tiles need to conform to /id/region/size/rotation/quality.format.

https://github.com/IIIF/awesome-iiif#image-server-shims

edsilv commented 8 years ago

To keep the server as essentially a "dumb pipe" you'd want a client-side js shim of some kind, rather than a ruby or similar one. Otherwise, everyone pinning this content on their IPFS node would also have to wrap it in a special image server, which kind of defeats the object of IPFS :-)

https://twitter.com/edsilv/status/691626389099913217

daviddias commented 7 years ago

Oh, wow! Just found this issue, didn't realize that there were conversations about IIIF before the work we did for this IIIF :)

So, what's next? :D.

edsilv commented 7 years ago

@diasdavid Decentralised IIIF Collections? :-)