-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Content addressed shared site storage? #564
Comments
I think the benefit would be minimal: js/css files recommended to be merged (so the hash does not match and the sizes are also negilable) and the data files are dynamic/unique you can use webtorrent to share big files between sites and adding built-in torrent client are also planned. |
Initial page-load might be somewhat longer for a zite, but there is always a time-space trade-off. And since zites are single-page-applications, the initial page-load might not be the most relevant performance metric. Anyways, I see and accept your argument. |
I would love a backend using IPFS. This would also easily enable always-online caching nodes (think of a server running an IPFS node and pinning content for you). |
@HelloZeroNet I guess this can now be closed in favor of #2192. |
Right now all sites store their files in separate folders, some of them contain identical files.
With an IPFS-like storage system there would be no data duplication.
Would zeronet benefit from this?
The text was updated successfully, but these errors were encountered: