Introduction to Web 3.0

Kasun Perera — Sun, 12 Jun 2022 11:34:42 +0000

If you're reading this, you have come across the word "Web 3.0" and trying to participate in the modern web. The internet is constantly changing as the technology advanced, and the internet we are experiencing today is going through a significant paradigm shift.

In this article, I will explain how the web has evolved, "what is web 3.0?", and why it matters to us.

As the name suggests, Web 3.0 is the third and latest phase of the internet, and Web 1.0 and Web 2.0 are the previous phases. There're unique defining characteristics for these shifts in the history of the internet.

Web 1.0

Read-Only (1990-2004)

Web 1.0 was the web's initial version, and this era's main feature was providing information. The participants were consumers of the content, and the developers who built websites were the creators. The websites contained information mainly in text or image format.

The Web 1.0 experience lacked interactive elements and served static content instead of dynamic content. You can consider Web 1.0 as the read-only (static) web.

Web 2.0

Read-Write (2004-now)

Web 2.0 is the current phase of the web that we have primarily experienced. With the rise of social media platforms, the internet shifted towards a dynamic web experience instead of a static nature.

In the Web 2.0 world, anyone can participate in content creation since most apps are built in a way that easily allows one to be a creator. Users can interact, write their content, and share it with an audience instead of only consuming the information.

Along with being dynamic, another prominent characteristic of Web 2.0 is centralization. This means the big tech giants/social media companies own our content and personal data as we create content and interact with their platforms. We're the original data owners, but they monetize personal information for advertisements and can shut down anything anytime.

Web 2.0 is great in most ways, but transparency, privacy, and single point of failure are some main issues we have to deal with Web 2.0 world. These issues arise from a centralized nature and are the main concerns currently driving the shift toward Web 3.0. So what exactly is Web 3.0?

Web 3.0

Read-Write-Own (The Future?)

Web 3.0 is the future iteration of the internet that aims to solve the issues in Web 2.0 by decentralization. This next generation of the internet is powered by blockchain technology and cryptocurrency. The aim of Web 3.0 is to provide users ownership and control over their data.

From what we've discussed so far, the main idea of Web 3.0 is to keep data decentralized using the blockchain instead of centralized in servers, as is the general practice of Web 2.0.

Moreover, another main component of Web 3.0 is dApps. As the name suggests, dApps are essentially decentralized applications. Web 2.0 applications run and store data on centralized servers and databases (usually hosted and managed on a single cloud service provider). Instead, Web 3.0 applications (dApps) run on blockchains, decentralized networks of peer-to-peer nodes.

The followings are the main characteristics of Web 3.0:

Decentralized: Ownership gets distributed among its builders and users instead of the centralized cooperations that controlled and owned the most of internet.
Permissionless: No one gets excluded or banned since everyone has equal access to the Web 3.0 world.
Trustless: It doesn't depend on trusted third parties to operate. It uses incentives and other economic mechanisms.
Native Built-In payments: Instead of depending on the complex and strict infrastructure of banks and payment processors, it uses cryptocurrency for spending and sending money online.

Why does it matter?

Ownership

In the Web 3.0 world, it allows for direct ownership of your assets through non-fungible tokens (NFTs). Once you stop participating in the platforms, you can trade or sell your in-platform items on open markets and regain their value. No one, not even the platform owners, has the power to take away your ownership.

E.g., In a Web 2.0 game, if you purchase an in-game item, it is bound to your game's account. If the game creators decide to delete or ban your account, you will lose all the valuable things you have purchased within the game. Also, you can lose the value you invested into the game if you stop playing the game. But in Web 3.0 games, your assets are tied into you through NFTs that no one has the power to take them down.

Censorship Resistance

In Web2.0 platforms, users can't freely share their content because they have to obey the rules that platforms have. Sometimes they remove the posts and ban accounts when the users don't follow their policies or when they change their policies. In this kind of scenario, all the reputation a creator earns within the platform will be gone. So there's a massive imbalance between the platforms and content creators.

But on Web3.0, you can take your reputation with you when you leave the platform as your data lives on the blockchain. So you don't have to depend on the platforms, and censorship resistance is a native feature of Web 3.0 platforms.

Identity

In the Web 2.0 world, it uses OAuth or email + password as authentication methods, and you almost always have to hand over personal information to create accounts. You would create an account for every platform you use. If you want to change the display name or profile picture, you have to do it across every account. Also, these platforms can lock you out of your entire online life with a single click.

The identity works differently in Web 3.0, and identities will be bound to the wallet addresses of the user. The wallet address is entirely anonymous unless the user decides to attach their identity to it publicly. Users can use the same wallet across multiple platforms (dApps), and their identity is transferrable. It helps them to build their reputation over time.

In Web 3.0, you have a single login across platforms that is secure, anonymous, and censorship-resistant.

Native Payments

Web 2.0 payments depend on the banks and other payment processors, excluding people without bank accounts or those who live in the wrong country. Also, they ask for personal information to set up accounts and take longer transaction times when sending money.

Web 3.0 uses cryptocurrencies to simplify these processes, and you can send money directly in the browser without needing a trusted third party.

Decentralized Autonomous Organizations (DAOs)

A DAO is a community-led entity with no central authority. It lets you coordinate decentralized ownership of a platform and make decisions about its future. DAOs are fully autonomous and transparent. This is a new way of building companies in Web 3.0.

Imagine that a new project is announced that solves a real problem, and anyone can participate from day one. Either you can be an investor or a builder of this project. The community state to release n number of tokens and give 15% to the early builders, put another 15% for sale to the public (Same as the stocks in companies) and keep the rest for future contributors and funding of the project. Token owners can use their tokens to vote on the project's future changes or sell their holdings to make money. If someone believes in the project, they can buy and hold ownership of it, and if the project is heading in the wrong way, they can signal it by selling their tokens. This is in contrast to purchasing equity in private or centralized businesses. The purchasers have complete transparency over the project because blockchain data are entirely public and open.

This is already happening in the Web 3.0 space. For example, Gitcoin allows developers to get paid in cryptocurrency for working on Open Source issues.

A Decentralized Future

There are numerous benefits of Web 3.0 in its current form, but the ecosystem must address many limitations like accessibility and user experience for it to grow.

The Web 3.0 ecosystem is young and quickly evolving. So, this is an excellent article to check out if you want to break into Web 3.0 development.

Introduction to Node.js

Kasun Perera — Sun, 20 Jun 2021 17:17:54 +0000

Node.js is a runtime environment for executing JavaScript code outside of a browser.

Before Node.js, JavaScript has long been used in web pages and run only by browsers. But now we can execute JavaScript code without a browser with the help of Node.js which is built on Chrome’s V8 JavaScript engine.

Here’s a formal definition as given on the nodejs.org

Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Node is ideal for building highly scalable, data-intensive, and real-time back-end services.

What's so special about Node.js?

Node.js is easy to get started and can be used for prototyping and agile development.
JavaScript everywhere. If you're a front-end developer who knows JavaScript, you can easily get started Node.js without learning a new programming language.
It also can be used for building superfast & highly scalable services. Node is used in production by large companies like Netflix, Uber, PayPal &, etc.
Node.js has the largest ecosystem of open-source libraries. There're a lot of free open source libraries out there that we can use to build our services.

Simple Node.js program.

First install node on your machine. There are many tutorials online to guide the installation based on your operating system.

Once you have installed Node.js, Create a file named server.js containing the following contents:

const http = require('http');

const hostname = '127.0.0.1';
const port = 3002;

const server = http.createServer((req, res) => {
  res.statusCode = 200;
  res.setHeader('Content-Type', 'text/plain');
  res.end('Hello World');
});

server.listen(port, hostname, () => {
  console.log(`Server running at http://${hostname}:${port}/`);
});

Now open your terminal, change the directory to the folder where the file is saved and run node server.js to start your web server.

Now, visit http://localhost:3002 and you will see a message saying "Hello World".

Cool! you’ve just written Hello World in Node.js.

Refer official documentation for a more comprehensive guide to getting started with Node.js.

Here's the Node.js timeline so far:

(source: nodejs.dev)

2009

Node.js is born
The first form of npm is created

2010

Express is born
Socket.io is born

2011

npm hits version 1.0
Larger companies start adopting Node.js: LinkedIn, Uber, etc.
hapi is born

2012

Adoption continues very rapidly

2013

First big blogging platform using Node.js: Ghost
Koa is born

2014

The Big Fork: io.js is a major fork of Node.js, with the goal of introducing ES6 support and moving faster

2015

The Node.js Foundation is born
IO.js is merged back into Node.js
npm introduces private modules
Node.js 4 (versions 1, 2 and 3 never previously released)

2016

The leftpad incident
Yarn is born
Node.js 6

2017

npm focuses more on security
Node.js 8
HTTP/2
V8 introduces Node.js in its testing suite, officially making Node.js a target for the JS engine, in addition to Chrome
3 billion npm downloads every week

2018

Node.js 10
ES modules.mjs experimental support
Node.js 11

2019

Node.js 12
Node.js 13

2020

Node.js 14
Node.js 15

2021

Node.js 16

Forem: Kasun Perera