-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IIIF #26
Comments
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 |
Possibly relevant: Cc: @klokan |
Using TMS would require a shim - if it's a IIIF tile source, the URIs of tiles need to conform to https://github.com/IIIF/awesome-iiif#image-server-shims |
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 :-) |
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. |
@diasdavid Decentralised IIIF Collections? :-) |
Goal: automate the process of getting IIIF manifests and assets into IPFS
Related: #25
The text was updated successfully, but these errors were encountered: