User Tools
web_hosting
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| web_hosting [10/11/2021 10:54] – created gfactor | web_hosting [04/27/2023 18:43] (current) – gfactor | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| Until the time that a static conversion tool is built within the Qortal UI, a website wishing to be hosted on Qortal that is not already static, will need to be converted first. There will be multiple tutorials provided on how to accomplish this until the conversion tool is built into the UI itself. Eventually, dynamic content will also be supported directly on Qortal hosting, but due to the added security concerns and added development necessary to facilitate adequate ‘sandboxing’ for those concerns to be nullified, dynamic content will be something that is released at a later date. | Until the time that a static conversion tool is built within the Qortal UI, a website wishing to be hosted on Qortal that is not already static, will need to be converted first. There will be multiple tutorials provided on how to accomplish this until the conversion tool is built into the UI itself. Eventually, dynamic content will also be supported directly on Qortal hosting, but due to the added security concerns and added development necessary to facilitate adequate ‘sandboxing’ for those concerns to be nullified, dynamic content will be something that is released at a later date. | ||
| - | Even with static content only, there are innumerable potential use cases and methods by which this static content can be used to derive websites and applications that are no different to the end user than ones that are dynamic. As seen in the above Qortal website demo, the visual and functional aspects of the website are identical to the original regardless of the fact that the site was converted to a static site. In most cases for user websites, blogs, and other such pages, there will be no difference to the end user between a site static and hosted on Qortal | + | Even with static content only, there are innumerable potential use cases and methods by which this static content can be used to derive websites and applications that are no different to the end user than ones that are dynamic. As seen in the above Qortal website demo, the visual and functional aspects of the website are identical to the original regardless of the fact that the site was converted to a static site. In most cases for user websites, blogs, and other such pages, there will be no difference to the end user between a site static and hosted on Qortal |
| - | Aside from the need for static content only initially, Qortal web hosting will be no different than traditional web hosting as far as the end user is concerned. The only difference is that the user will access it through a Qortal node or a Qortal node acting as a proxy (as the above demo shows). The end user won’t be able to see the differences that make Qortal web hosting | + | Aside from the need for static content only initially, Qortal web hosting will be no different than traditional web hosting as far as the end user is concerned. The only difference is that the user will access it through a Qortal node or a Qortal node acting as a proxy (as the above demo shows). The end user won’t be able to see the differences that make Qortal web hosting |
| Qortal hosted websites will be ‘unhackable’ in the traditional sense, as the content on a Qortal namespace can literally only be edited by the account that put it there. Therefore there is no possible way for any other user to modify that data. The data will also be redundant based on how many viewers of the website there have been (who are also data nodes). Every data node that views a Qortal website, will become a peer for that website by default. Every data node follower of a website’s namespace will become a peer for that website’s namespace by default. Therefore the more people who view a website, the more copies of that website exist. This makes the content more redundant and faster for the content to be distributed to subsequent viewers. It is an amazing system that will be completely FREE to use. | Qortal hosted websites will be ‘unhackable’ in the traditional sense, as the content on a Qortal namespace can literally only be edited by the account that put it there. Therefore there is no possible way for any other user to modify that data. The data will also be redundant based on how many viewers of the website there have been (who are also data nodes). Every data node that views a Qortal website, will become a peer for that website by default. Every data node follower of a website’s namespace will become a peer for that website’s namespace by default. Therefore the more people who view a website, the more copies of that website exist. This makes the content more redundant and faster for the content to be distributed to subsequent viewers. It is an amazing system that will be completely FREE to use. | ||
| Line 17: | Line 17: | ||
| As development continues, the use of QORT on the data chain will be possible and then some sort of ‘pay per extra copy’ structure could be set up on Qortal. The creators who do not have enough followers or viewers, or would simply like a few extra copies of their data hosted, can browse a ‘data market’ with data nodes with an algorithmically defined ‘reputation’ and pay to have the extra redundancy of their data. | As development continues, the use of QORT on the data chain will be possible and then some sort of ‘pay per extra copy’ structure could be set up on Qortal. The creators who do not have enough followers or viewers, or would simply like a few extra copies of their data hosted, can browse a ‘data market’ with data nodes with an algorithmically defined ‘reputation’ and pay to have the extra redundancy of their data. | ||
| + | |||
| + | More info can be found on the [[Qortal Data Network (QDN)]] page. | ||
web_hosting.1633964068.txt.gz · Last modified: 10/11/2021 10:54 by gfactor