A Pipe-Dream about Decentralized Web?

No Comment Yet

(..) Have you ever had a Dream so real (…)

(..) or wait a sec (..) Could it be real? Could we have a ⋮⋮⋮ World Wide Web?  (..) Wizards already came up with things like the very first Sybil-proof data-exchange incentivization protocol for arbitrary computer networks (..) seems like it could come in-use to aid the cause (..) couldn’t they just deliver.. little more?  (..) Fill-in the missing gaps?

(..) Couldn’t they just use their Wands?(..)🤭

Today, you will get equipped with a Wand of your own.

🌟A Pipe Dream Becoming a Reality

(..) Towards the Glory of decentralization we shall be movin’ on as one.

Heads Up: This article boards a tutorial which takes you by hand over deploying your very first ⋮⋮⋮ website. To deploy a website with customized, personal information, simply provide values of your choosing.

Haven’t we all heard about ‘Web 3.0’? With ICOs and entire projects presumably concentrating around the very issue alone?

Truth be told, to make decentralized web a reality, it took Wizards a single 15 hour long programming marathon.

How could that be?  you ask?

The answer is – a proper architecture. See, we have been implementing ⋮⋮⋮ GRIDNET OS as a multipurpose, decentralized operating system.

What does that really mean? At the design stage, we were not concerned much about particular end-user applications or business logic.

What we were concerned with though, was allowing for unprecedented, decentralized experience with limitless possibilities, reassembling as much as possible those you know from centralized IT systems.

From our perspective, thus, decentralized World Wide Web is just a single use-case scenario.

(..) We have already brought to the table lots more than needed to make a ⋮⋮⋮World Wide Web a reality.

In fact, the  ⋮⋮⋮ Web-UI employs much more sophistication. It uses advanced binary-mode data-encoding, data encapsulation, cryptography, onion routing (..) way more than needed to make ⋮⋮⋮ Web a reality.

The Wizardous Crypto-incentivized Web-Proxy apparatus is yet another thing that comes to one’s head (..) then, the very first on the planet crypto-incentivized ⋮⋮⋮ Web-RTC Swarms,- ones not needing any kind of signaling servers  (in practical implementations bare-bone Web-RTC always used to need one). The list goes on and on.

Then, nothing would be possible without ⋮⋮⋮ Hexi🤖 (..) of course.

(..) and no (..) She did not make us say so! 😆

Why? Hexi🤖 is a manifestation, a realisation, if you will, of a pipe-dream (oh Rejoice!) about allowing for asynchronous, ad hoc authenticated, remote code execution.

Without it, nothing you see around here would be possible. It is one of the main reasons Ethereum and friends wouldn’t be catching up with us anytime soon. Indeed, the mobile app is the only trusted element, allowing for deferred authentication of actions performed within the system. For those not aware, ‘Hexi’, she is the onboard ‘AI’ running on the mobile app.

All the functional and system-interaction scenarios required a brand new architectural approach, along with a brand new programming language, which would accommodate the requirements, including a control-flow logic in which user ‘logs-on’, does any arbitrary actions (either through SSH, the ⋮⋮⋮ Web-UI or both) at the end (or in the middle) of a session scans a single QR code to commit, and is on his way.

 (..) bits and bytes (..) the zeroes and ones (..) these are all around. These are around. Rejoice!

Enough pep-talk! Enough shilling! Let us get some hands on experience on how we could deploy (..) wait a sec (..)  ⋮⋮⋮ Decentralized State-Domains.. wasn’t the term used by Wizards for quite some time already?  And indeed! Check out research paper available over here. If you ever feel like what you are seeing feels sort of sci-fi, always remember, it is just a beginning. We might have departed far ahead of architecture such as Ethereum let alone Bitcoin (..) but we do still clearly see what lies ahead. Rejoice!

Downsides of Centralized Web include:

  • You can be tracked. (usually we use Onion Routing and proxies to cope with that)
  • Content is operated by a centralized entity who can bring it down anytime he feels like doing so.
  • It is difficult for people to get involved in contributing, by helping to maintain a website or web-service. Talk about ⋮⋮⋮ YouTube. Not a simple webpage with a  Donate button.
  • From the perspective of end-user, a couple of service providers are required. The ISP, the DNS provided, also some software (web-server) usually needs to be installed.

Hold on (..) Wizards  do not like the idea of Internet Service Providers(ISPs)?  You might not know that.. but long, long time ago (..)

In fact (..) before the idea of ⋮⋮⋮ GRIDNET OS  had materialized (..) some of us were mainly concerned with data-exchange. To cut it short, ⋮⋮⋮ GRIDNET OS  has been designed from the ground-up to withstand any kind of apocalypse. (..) wait a sec (..) were Wizards the first to come up with a ⋮⋮⋮ decentralized architecture for the power industry? Published at one of the most prominent conferences in the field? Look it up over here and Rejoice!

🌟Wizardous Solution?

⋮⋮⋮ Decentralized State-Domains. In short, we have now made it possible for each ⋮⋮⋮ State-Domain to act as a home directory for a web-server embedded into ⋮⋮⋮ GRIDNET Core.

By following this tutorial, you will get to know how to deploy a ⋮⋮⋮ decentralized web-site of your own.

Prerequisites 

  • ⋮⋮⋮ State-Domain, preferably with a ⋮⋮⋮ Friendly ID registered as your friendly ID now effectively constitutes your ⋮⋮⋮  Decentralized Web-Site URL.
    If you still own neither of these, head immediately to a tutorial available over here. Remember! Friendly IDs and your current account balances are to make it to LIVE-Net, thus it is always good to have a fancy Friendly ID registered. Think of centralized Web-Domains in early 90s. Good names are now worth quite a lot.

(..) grab a fancy ⋮⋮⋮ Friendly ID of yours while lots of fancy ‘short URLs’ remain! Wizards do not charge you anything. Pick what you will and keep your private-key secret. That’s about it. Let your friends know, they would surely thank you later.

  • ⋮⋮⋮ Hexi🤖 running on either Android or iOS

Tutorial

Let’s go. We will be using ⋮⋮⋮ State-Domain ICOFund. You may replace it with a ⋮⋮⋮ Friendly ID, associated with a ⋮⋮⋮ State-Domain of yours.

 

  1. First we will go about CDing into our ⋮⋮⋮ State-Domain.

    Feeling at home?

  2. Recall that we may list files at any time with LS. Now, we want the results of our actions to affect a permanent effect on ⋮⋮⋮ , so proceed with BT (Begin Thread) like so:

    begin decentralized thread’s formulation.

  3. Now, we need to prepare a HTML file to be served by ⋮⋮⋮ Decentralized Web-Service, which expects, by default, a file called index.html You may create and upload any files you wish (uploading would be much easier through Web-UI where all it takes is a simple drag-and-drop from native operating system). If you choose to use other filename than what’s expected by default then you would simply need to use an absolute ⋮⋮⋮ URL, when pointing other users to your content ex. https://148.251.75.24/s/ICOFund/index.html where index.html  may be an arbitrary file (video/image etc.).Now, let us prepare a simple HTML document. Web-UI boards the Editor UI dApp which would allow you to create and edit your web-page in a WYSIWYG manner, but since it is not public yet, you may choose to use any text-editor you wish. We came up with the following HTML markup:

    HTML markup of a simple web-page.

  4. How about uploading the file to your state-domain over SSH? We could have typed text by hand which could be pretty tedious. If you attempt to copy and paste a large amount of text over to a  ⋮⋮⋮ SSH Session, you are most likely to experience ⋮⋮⋮Firewall kicking in, as it boards some autonomous heuristics protecting full-nodes against abuse. Also, should you wish to use some fancy UNICODE characters, it just may turn out that your SSH client does not support these. So how?
    For starters, we’ll be using the ⋮⋮⋮ CAT utility. If you type CAT alone, a help-page would be shown.

    In-line help page of CAT.

    Here we quickly notice that  ⋮⋮⋮ CAT does automatic base64Encoding detection More! if we paste base64encoded data, it is guaranteed that once data makes it into the decentralized state-machine, it would be automatically decoded, saving up on storage.

  5. In order to make storage of your website cheaper you might want to ‘minify’ your HTML first. The process removes unnecessary whitespaces. You may want to use https://www.willpeavy.com/tools/minifier/

    HTML web-page minified.

  6. After having minified your webpage, encode the result with https://www.utilities-online.info/base64.
    Paste your code into the text-field to the left and hit Encode. The result would appear to the right, as follows:

    base-64 encoded, minified HTML markup is to the right.

  7. Great! Getting back to ⋮⋮⋮ GRIDNET OS. apps available from the ⋮⋮⋮Decentralized Web-UI would have taken care of all of the above for you. Here, we are dealing with ⋮⋮⋮SSH sessions though. Let us get it work for us. We need to paste contents of the right field above (base64 encoded output) to the terminal as a parameter to ⋮⋮⋮CUT. We recommended doing so at most 3 lines at a time to avoid firewall kicking on. The result should look look below:

    If you you  ⋮⋮⋮ LESS index.html you will get to see that the file already contains decoded data:
  8. Now, all it takes is to commit with ⋮⋮⋮ CT, the usual way.
  9. Congratulations! After completed you may point your web-browser directly your brand- new decentralized webpage!  Here it would be https://test.gridnet.org/s/ICOFund.

Note: Your ⋮⋮⋮ State-Domain serves as a home-directory to full-fledged decentralized  ⋮⋮⋮ Web-Service. The final URL under which your website would be available follows the below syntax:

https:// [Full-Node’s IP] /s/ [FriendlyID]

ex. https://test.gridnet.org/s/ICOFund or https://148.251.75.24/s/ICOFund

Remember the tutorial in which we have deployed an ⋮⋮⋮ NFT? Now we may access it through the ⋮⋮⋮ Web-Service easily! https://test.gridnet.org/s/ICOFund/magicCat.webp

🌟Homework

Deploy a Decentralized Web-Page of your own,  share it on Twitter and receive 50 GNC for doing so.

The Old Wizard🧙 once said :”(..) remember (..) Remember to spread the Word🕊️ (..)”

 

GRIDNET

Author

GRIDNET

Up Next

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *