This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
qdn_updates [07/21/2022 05:35] – gfactor | qdn_updates [09/05/2023 05:21] (current) – Made more generic instead of mentioning my username caldescent | ||
---|---|---|---|
Line 4: | Line 4: | ||
Listed from most recent to oldest: | Listed from most recent to oldest: | ||
- | ===== Notes From CalDescent | + | ===== Developer |
The idea of a separate "data node" was a possibility in the early stages of development, | The idea of a separate "data node" was a possibility in the early stages of development, | ||
Line 18: | Line 18: | ||
(or, we can fit more data transactions in each block if we increase chunk sizes and keep the total file size limit the same). | (or, we can fit more data transactions in each block if we increase chunk sizes and keep the total file size limit the same). | ||
- | ===== Notes From CalDescent | + | ===== Developer |
Each website is broken up into chunks (currently 1MB each but will probably increase to 2MB+ at some point), and these chunks can be distributed in any way we choose. You could have one chunk per node, or all chunks on all nodes, or anything in between. The system pieces them together from all over the world when it needs to build the website back into its original state. The actual logic of the distribution of chunks is yet to be implemented; | Each website is broken up into chunks (currently 1MB each but will probably increase to 2MB+ at some point), and these chunks can be distributed in any way we choose. You could have one chunk per node, or all chunks on all nodes, or anything in between. The system pieces them together from all over the world when it needs to build the website back into its original state. The actual logic of the distribution of chunks is yet to be implemented; | ||
Line 32: | Line 32: | ||
We may have an opt-in setting to allow you to become a " | We may have an opt-in setting to allow you to become a " | ||
- | ===== Notes From CalDescent | + | ===== Developer |
The files are " | The files are " | ||
Line 54: | Line 54: | ||
I’m planning on having a “storage policy” setting with various different possible values such as following only / viewed only / following and viewed / all / none. Then we can default to following and viewed, and people have the option of increasing or reducing the scope of their storage. I’ll be working on this part in the next few weeks. | I’m planning on having a “storage policy” setting with various different possible values such as following only / viewed only / following and viewed / all / none. Then we can default to following and viewed, and people have the option of increasing or reducing the scope of their storage. I’ll be working on this part in the next few weeks. | ||
- | ===== Notes From CalDescent | + | ===== Developer |
- | For anyone interested in checking out the progress, you can do so here: https:// | + | We already have a fully operational decentralized storage system. |
- | + | ||
- | You will see that we already have a fully operational decentralized storage system. | + | |
The most recent feature introduces layering - similar to Docker - so that on-chain updates can be published to existing sites/ | The most recent feature introduces layering - similar to Docker - so that on-chain updates can be published to existing sites/ |