From 4818fc42346c2eed02d7191a2b7c3faee2603805 Mon Sep 17 00:00:00 2001 From: Derrick Hammer Date: Sat, 30 Sep 2023 02:04:59 -0400 Subject: [PATCH 1/2] fix: typo --- docs/web3-building-blocks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/web3-building-blocks.md b/docs/web3-building-blocks.md index 424004f..bae741f 100644 --- a/docs/web3-building-blocks.md +++ b/docs/web3-building-blocks.md @@ -25,7 +25,7 @@ So instead of trying to explain what Web3 involves, lets explain what we have in - `Virtual Private Server (VPS) -> Compute Networks` - A few of these exist, but there are blockchain networks that specialize in the brokering of compute services like you may expect from AWS, which can run pretty much anything else in Web3 if needed. Both Web2 and Web3 have P2P networks, and the best known are probably BitTorrent and IPFS. These can be viewed as the content networks (not blockchains) and are extremely important for Web3. - `Serverless Functions and CDNs -> Edge Networks` - These are a specialization of compute networks that were born from AWS with lambada (and cloudfront) but has since rapidly evolved. There are projects that are experimenting with blockchain based edge compute and CDNs. -- `NAS Backups, Archiving, Object Storage -> Storage Neworks` - If the currency of the world is currently oil, the currency of the web is data. No matter what you do, you eventually need secure, private, encrypted data storage, and a lot of it. This comes in many forms, but broadly these are where all of Web3's (and Web2) data will end up in sooner or later. +- `NAS Backups, Archiving, Object Storage -> Storage Networks` - If the currency of the world is currently oil, the currency of the web is data. No matter what you do, you eventually need secure, private, encrypted data storage, and a lot of it. This comes in many forms, but broadly these are where all of Web3's (and Web2) data will end up in sooner or later. Web3 is also fundamentally built on P2P networks in many forms and designs. Every blockchain alone is a P2P network, tracking its databases changes. That's very different from Web2, that is mostly using `server -> client` model. From 64876ab9d200909ed5adf0a7e5b49194833089ae Mon Sep 17 00:00:00 2001 From: semantic-release-bot Date: Sat, 30 Sep 2023 06:06:34 +0000 Subject: [PATCH 2/2] chore(release): 0.1.0-develop.4 [skip ci] # [0.1.0-develop.4](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.1.0-develop.3...v0.1.0-develop.4) (2023-09-30) ### Bug Fixes * typo ([4818fc4](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/4818fc42346c2eed02d7191a2b7c3faee2603805)) --- CHANGELOG.md | 7 +++++++ package.json | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9140d31..72ca755 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,10 @@ +# [0.1.0-develop.4](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.1.0-develop.3...v0.1.0-develop.4) (2023-09-30) + + +### Bug Fixes + +* typo ([4818fc4](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/4818fc42346c2eed02d7191a2b7c3faee2603805)) + # [0.1.0-develop.3](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.1.0-develop.2...v0.1.0-develop.3) (2023-09-30) diff --git a/package.json b/package.json index 1dc529c..e732660 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@lumeweb/docs.lumeweb.com", - "version": "0.1.0-develop.3", + "version": "0.1.0-develop.4", "private": true, "repository": { "type": "git",