Skip to content
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

Consider IPFS integration #33

Closed
kumavis opened this issue Jan 5, 2016 · 2 comments
Closed

Consider IPFS integration #33

kumavis opened this issue Jan 5, 2016 · 2 comments

Comments

@kumavis
Copy link

kumavis commented Jan 5, 2016

IPFS is an open-source protocol for content-addressable storage.

https://www.youtube.com/watch?v=skMTdSEaCtA

Utilitarian reasons to use IPFS:

  • massive storage savings: all repeated assets are stored once ( e.g. repeated exact version of jquery or an image )
  • massive bandwidth savings: the community you serve can safely and reliably distribute the assets on your behalf
@ikreymer
Copy link
Collaborator

ikreymer commented Jan 5, 2016

Already being considered :) See: ipfs-inactive/archives#28 and ipfs/apps#3
Current issue is to figure out best way to store WARC records into IPFS, since Webrecorder saves HTTP traffic, including HTTP headers, not just files, and is the standard format in web archiving.

I made an experimental add-on to pywb library that writes WARCs to IPFS: https://github.com/ikreymer/pywb-ipfs

Not sure this is the best way yet, though.
Once we have WARC in IPFS figured out, this will be much easier.

There are also privacy issues, some users may want to keep things private, and/or have option to delete pages, and will probably want a different storage backend for that.

@kumavis
Copy link
Author

kumavis commented Jan 5, 2016

fantastic! I'll close this

@kumavis kumavis closed this as completed Jan 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants