Merge branch 'develop'

This commit is contained in:
Derrick Hammer 2023-11-01 04:37:41 -04:00
commit ecedf2e963
Signed by: pcfreak30
GPG Key ID: C997C339BE476FF2
3 changed files with 9 additions and 2 deletions

View File

@ -1,3 +1,10 @@
## [0.1.4-develop.2](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.1.4-develop.1...v0.1.4-develop.2) (2023-11-01)
### Bug Fixes
* grammar ([b2912ae](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/b2912aee2649cf69ea7593ce5c8dd21876276838))
## [0.1.4-develop.1](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.1.3...v0.1.4-develop.1) (2023-11-01)

View File

@ -52,7 +52,7 @@ Most of the world would roll over and comply anyway since its what people always
The whole trajectory of Web3 needs to go past short-term casino games, centralization of its infrastructure, and a Microsoft EEE mentality in the DeFi space. Only then can we start to get real value for users to care.
Our view is that, if you use Web3, and you don't notice it is any different to Web 2.0, it is boring and *"just is"*, only then the Web3 is can be considered a success. An open web needs to be the `standard`, not the exception.
Our view is that, if you use Web3, and you don't notice it is any different to Web 2.0, it is boring and *"just is"*, only then the Web3 can be considered a success. An open web needs to be the `standard`, not the exception.
And that starts with `access`. Your network can be the most decentralized ever, but if no one can easily access it, does it matter? This is the last mile issue of Web3. We have all this infrastructure, centralized or decentralized, but access is still a barrier, and frankly... it's a joke.

View File

@ -1,6 +1,6 @@
{
"name": "@lumeweb/docs.lumeweb.com",
"version": "0.1.4-develop.1",
"version": "0.1.4-develop.2",
"private": true,
"repository": {
"type": "git",