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

[ New Feature ] Block Storage for File Objects #10

Open
canewsin opened this issue Mar 29, 2022 · 0 comments
Open

[ New Feature ] Block Storage for File Objects #10

canewsin opened this issue Mar 29, 2022 · 0 comments

Comments

@canewsin
Copy link
Collaborator

Background:

Current ZeroNet Storage Acts as single place for single site, means all site files stored in Site Directory. This is convenience for user to browse files, but most users don't browse or aware of Zite System internals. After Introduction for browse files feature in sidebar, users tend to use that instead of manually browsing site dir.

Cons of Current Storage:

File Duplication for both site side resources as well as user storage due to the fact that he needs to host exact same file twice.
Network availability, since files are treated as 2 separate files, availability of file is low on network, even same file has high availability on another site.

Solution:

Block Storage for File Objects, Each File has sha512 hash in content.json, So using this site Files are stored at single directory, only files exists in site are manifest files(content.json etc.) and files that are marked as ignored in content.json. These files can be encrypted using user side keys to protect files from malicious access which inturn benifits the user. On user side, Only change they see is different storage system from existing one, but user can choose to turn off this for own/single/all sites or for small files, for eg site devs who use IDE for site development.

canewsin added a commit that referenced this issue Mar 29, 2022
canewsin added a commit that referenced this issue Mar 29, 2022
@canewsin canewsin pinned this issue Aug 4, 2022
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

1 participant