User Tools
node_types
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| node_types [06/28/2025 17:04] – crowetic | node_types [03/21/2026 14:52] (current) – ironfixxxer | ||
|---|---|---|---|
| Line 26: | Line 26: | ||
| The first concept to implement is that the only data to be hosted on a user’s data node, is the data that the user of the node viewed or follows. A data node user who views a website or anything hosted on a data namespace will become a ‘peer’ for that data (hosting a copy of it on their data node as well). This system functions very similarly to that of the ‘torrent’ network, wherein users are ‘peers’ for data they have downloaded unless they choose to remove that data and others then download the data from them and become a peer for it once it is completed. | The first concept to implement is that the only data to be hosted on a user’s data node, is the data that the user of the node viewed or follows. A data node user who views a website or anything hosted on a data namespace will become a ‘peer’ for that data (hosting a copy of it on their data node as well). This system functions very similarly to that of the ‘torrent’ network, wherein users are ‘peers’ for data they have downloaded unless they choose to remove that data and others then download the data from them and become a peer for it once it is completed. | ||
| - | Data nodes only the data they choose to have on their node. If the data node views a website, then after viewing it decides they do NOT want to be a peer for that website (they don’t want to host a redundant copy of that website for the website creator), they can subsequently delete the website from their data node, and will no longer hold the data nor continue being a peer for others to download that data. Full individual control over every bit of the data on a user’s node is absolutely essential to Qortal’s functionality. Individual sovereignty over EVERYTHING in Qortal is the end goal. Therefore full control over the data that is stored on the user’s data node is required. There is no data on any user’s node that the user is not aware of. | + | Data nodes share only the data they choose to have on their node. If the data node views a website, then after viewing it decides they do NOT want to be a peer for that website (they don’t want to host a redundant copy of that website for the website creator), they can subsequently delete the website from their data node, and will no longer hold the data nor continue being a peer for others to download that data. Full individual control over every bit of the data on a user’s node is absolutely essential to Qortal’s functionality. Individual sovereignty over EVERYTHING in Qortal is the end goal. Therefore full control over the data that is stored on the user’s data node is required. There is no data on any user’s node that the user is not aware of. Use the Q-App, **Host Monitor Plus** to view and manage your shared data. |
| - | The concept of ‘following’ has been used in many social media platforms for years. This concept is that of essentially ‘paying attention’ to a certain user and what they do. Following in terms of Qortal data storage will be similar, but slightly different. In Qortal, a data node will have the option to ‘follow’ a content creator’s namespace. If the data node chooses to become a follower of that namespace, they will subsequently automatically become a peer for the data that namespace puts up. If a data node likes the content of a certain website, following that website would bolster the availability of the website to others automatically. Becoming another redundant copy of that website’s data for the creator is a substantial way to support the creator. | + | The concept of ‘following’ has been used in many social media platforms for years. This concept is that of essentially ‘paying attention’ to a certain user and what they do. Following in terms of Qortal data storage will be similar, but slightly different. In Qortal, a data node will have the option to ‘follow’ a content creator’s namespace. If the data node chooses to become a follower of that namespace, they will subsequently automatically become a peer for the data that namespace puts up. If a data node likes the content of a certain website, following that website would bolster the availability of the website to others automatically. Becoming another redundant copy of that website’s data for the creator is a substantial way to support the creator. Use the Q-App, **Q-Follow** to follow and block names/ |
| Following also opens up many other unique opportunities, | Following also opens up many other unique opportunities, | ||
node_types.txt · Last modified: 03/21/2026 14:52 by ironfixxxer