Compare commits
No commits in common. "0c65b6d35d7e8ab3fcf008855950065a8cdcd776" and "a9eab943a596e118efda07d7576659ca3aeb36ee" have entirely different histories.
0c65b6d35d
...
a9eab943a5
33
CHANGELOG.md
33
CHANGELOG.md
|
|
@ -1,35 +1,4 @@
|
|||
# [0.3.0-develop.4](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.3.0-develop.3...v0.3.0-develop.4) (2023-11-15)
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* formatting and header size changes ([993d384](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/993d38456cfff350d7dd31174732a45de2e27caa))
|
||||
|
||||
|
||||
### Features
|
||||
|
||||
* add roadmap ([7694546](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/7694546aa1b19b6431f780e4e5a75e2be407d544))
|
||||
|
||||
# [0.3.0-develop.3](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.3.0-develop.2...v0.3.0-develop.3) (2023-11-15)
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* ensure trailing slashes get a redirect ([d4018c2](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/d4018c2b2d51616102cadbf5633b0d722769b997))
|
||||
|
||||
# [0.3.0-develop.2](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.3.0-develop.1...v0.3.0-develop.2) (2023-11-15)
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* bad redirect ([d1a052c](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/d1a052c2bce749426e817291e75b23461e24dbf9))
|
||||
|
||||
# [0.3.0-develop.1](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.2.1...v0.3.0-develop.1) (2023-11-15)
|
||||
|
||||
|
||||
### Bug Fixes
|
||||
|
||||
* broken link ([bc56dfa](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/commit/bc56dfa573a44438bd7bebdb1e4c22b7c0563544))
|
||||
# [0.3.0](https://git.lumeweb.com/LumeWeb/docs.lumeweb.com/compare/v0.2.1...v0.3.0) (2023-11-10)
|
||||
|
||||
|
||||
### Features
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: Making a Better Web
|
|||
|
||||
Want to hear a joke?
|
||||
|
||||
#### Web3.
|
||||
## Web3.
|
||||
|
||||
Probably not the start you expected, but let's be honest with ourselves for a moment - the current state of web3 is a joke, at least to the majority of the world.
|
||||
|
||||
|
|
@ -14,16 +14,16 @@ On the other side there is the Bitcoin, it doesn't care, it just works as it's m
|
|||
|
||||
So, what's next? Maybe to better understand this all, let's rewind a bit and learn from our past first.
|
||||
|
||||
#### Web 1.0
|
||||
### Web 1.0
|
||||
|
||||
This era started in early 90s and marks a first generation of the world wide web, aka internet. It was `open` and had an `unlimited potential`. Number of users was growing exponentially, as was the number of companies building in the space and it didn't take too long for few big ones to emerge and people just happily handing control of own data over to them.
|
||||
|
||||
#### Web 2.0
|
||||
### Web 2.0
|
||||
|
||||
By 2005, the internet was becoming increasingly centralized and this transition was complete with arrival of massive social networks connecting billions of people around the globe and monetizing their voluntarily entered and frequently updated personal data. On Web 2.0, the user is the real `product` and your data are no longer yours, same as your money on a bank account are not yours, you only trust a third party to manage it for you.
|
||||
|
||||
|
||||
#### Web3?
|
||||
### Web3?
|
||||
|
||||
Web3 as an ideal is supposed to be about you, `the user`, not you, `the builder`. I have seen various ideas suggesting Web3 is `read + write + own`, and I can largely agree, though many builders don't agree with the route to achieve that.
|
||||
|
||||
|
|
@ -2,13 +2,13 @@
|
|||
title: Web3 Browser Web App
|
||||
---
|
||||
|
||||
|
||||
Link: https://web3browser.io
|
||||
|
||||
**Link**: https://web3browser.io
|
||||
|
||||
|
||||
This is an experimental tech demo to enable HNS and ENS browsing via IPFS.
|
||||
|
||||
**This demo uses the following technologies**:
|
||||
This demo uses the following technologies:
|
||||
|
||||
* Hypercore: https://docs.holepunch.to/
|
||||
* The kernel, forked from Skynet: https://git.lumeweb.com/LumeWeb/libkernel/src/branch/develop
|
||||
|
|
@ -18,7 +18,7 @@ This is an experimental tech demo to enable HNS and ENS browsing via IPFS.
|
|||
* IPFS: https://github.com/ipfs/helia
|
||||
* HNS: https://github.com/handshake-org/hsd
|
||||
|
||||
**Some notes about current issues and limitations**:
|
||||
Some notes about current issues and limitations:
|
||||
|
||||
* IP addresses are not supported. So you cannot access "normal" servers.
|
||||
* Pages may render twice, as in refresh, before loading.
|
||||
|
|
@ -9,3 +9,28 @@ This project was created so that we can have a *true* open web in which we can s
|
|||
We are doing `progressive decentralization`. This means that at this time, while the tech itself uses P2P technology and is decentralized, the products we create are semi-centralized.
|
||||
|
||||
---
|
||||
|
||||
**The following is an AI generated summary of these docs**
|
||||
|
||||
The Lume Web Protocol is an innovative approach to navigating the ever-evolving internet landscape, particularly in the transition from Web 2.0 to Web3. Lume's development was initially inspired while creating a Web3 cloud drive on Nextcloud based on Skynet. However, the focus shifted to addressing the fundamental issue of content access in the Web3 environment.
|
||||
|
||||
### Web 2.0 and Web3 Evolution
|
||||
|
||||
- **Web 1.0 and 2.0**: The early web (Web 1.0) was open and had unlimited potential, but it eventually led to centralization, especially with the rise of massive social networks around 2005. This centralization meant that users essentially became products, with their personal data monetized by these platforms.
|
||||
- **Web3 Ideals**: Web3 aims to shift the focus back to the user, advocating for a creator economy and peer-to-peer interactions, with an emphasis on privacy and data ownership. Despite this, the practical implementation of Web3 has faced challenges, such as reliance on centralized storage and the influence of venture capital, which sometimes contradicts the ethos of decentralization.
|
||||
- **Infrastructure Vulnerabilities**: A significant concern in the Web3 space is the centralized nature of key internet infrastructure components like AWS/Google, Cloudflare, and ICANN, which could pose risks to the stability and independence of Web3 initiatives.
|
||||
- **Vision for Web3**: The ideal Web3 should be indistinguishable from Web 2.0 in terms of user experience, with an emphasis on open standards and easy access, overcoming the current accessibility barriers.
|
||||
|
||||
### Limitations of Web2 and the Shift to Web3
|
||||
|
||||
- **Protocols**: Web2 relies on protocols like HTTP, FTP, SMTP, IMAP, POP, and DNS, but these often have single points of failure and are susceptible to control by large technology companies and censorship at various levels.
|
||||
- **Web3 Transformations**: Web3 aims to transform these components, with blockchain replacing traditional money ledgers, smart contracts substituting stored procedures, distributed databases taking the place of traditional SQL/NoSQL databases, and P2P networks replacing server-client models. This shift is fundamental to the Web3 architecture, focusing on decentralization and resistance to censorship.
|
||||
|
||||
### Lume's Role in the Web3 Landscape
|
||||
|
||||
- **P2P Network**: Lume functions as a P2P network using public keys, akin to BitTorrent but tailored for Web3. It's designed as a bridge to service all Web3 needs and is not based on blockchain technology.
|
||||
- **Storage and Gateway**: Lume acts as a storage portal, building on Sia for private and public data storage, and serves as a gateway for users to interface with various content networks and blockchains.
|
||||
- **Middleware System**: As a middleware system, Lume facilitates access to other networks through a relay network, employing technologies like Hypercore/Dat for anonymous access and providing DNS services.
|
||||
- **Frontend and Content Networks**: Lume's browser technology, similar to kernel and kernel modules in Linux, supports light clients, SPV nodes, and DNS resolvers among others. It utilizes content identifiers (CIDs) and supports real-time verified streaming.
|
||||
|
||||
In summary, Lume is designed to address the centralization and censorship issues prevalent in Web2, offering a decentralized, user-centric platform that aligns with the ethos of Web3. It bridges traditional internet protocols with their Web3 counterparts, and through its P2P network, storage solutions, and middleware systems, Lume aims to enhance data ownership, decentralization, and accessibility in the digital space.
|
||||
|
|
|
|||
|
|
@ -1,16 +0,0 @@
|
|||
---
|
||||
title: What is Lume?
|
||||
---
|
||||
|
||||
`What is Lume?` This is something we have often asked ourselves to explain it 😅.
|
||||
|
||||
Lume can be broken down into a few major focuses:
|
||||
|
||||
- Lume is a **P2P network** that uses public keys instead of torrent hashes to access peers and content.
|
||||
- Like a BitTorrent, but ready for Web3. You can also see it to be a bit like IPFS which uses Libp2p, but more light weight.
|
||||
- The goal here is to create a bridge P2P network `to service all of Web3`.
|
||||
- `It's NOT a blockchain`. You don't need one since anyone can provide services with RPC or their own custom protocol, and anyone can query them.
|
||||
- Lume is a **storage portal** (think `L2` in blockchain terms).
|
||||
- It builds on Sia and stores your private data, and eventually public. In other words think of it like a paid IPFS service, but its not IPFS.
|
||||
- Lume is the **end user gateway**.
|
||||
- It is how you will interface with all content networks, blockchains, or other nets in the future. This could be a browser extension, web browser itself or anything in-between.
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
---
|
||||
title: History
|
||||
---
|
||||
|
||||
Lume started (before we even decided it was a project or the name) while we were trying to create a web3 cloud drive on Nextcloud based on Skynet. We realized that we were going down the wrong path and needed to solve accessing content before doing anything with the content itself.
|
||||
|
||||
Skynet in the process had a very rough year, as since 2020, Skynet tried to solve distribution with network of Skynet Portals, but experienced number of obstacles from all levels of internet infrastructure (see [Limitations of Web2](/problems/web2-limits.md)) and eventually was shut down.
|
||||
|
||||
Sia in the background was trying to support both innovating and Skynets efforts, and things came to a head with Skynet going bankrupt.
|
||||
|
||||
In that journey, Lume has pivoted at-least 1 time to meet its goals, and has ended up having to build many building blocks out of necessity, and a few that may go unused 🙃.
|
||||
|
||||
Sia has since started rebuilding with new software, and Lume has been building on top.
|
||||
|
||||
Sia is the network of the worlds data, and Handshake replaces ICANN while collaborating with the web3 ecosystem. We have discussed Sia a lot so far, but let it also be known the Handshake tribe has had its own share of drama too, and Lume is actively involved in both.
|
||||
|
||||
So the rabbit hole of Web3 DNS is where we started as the origin of Lume, which means the `world` or `light` in Romanian. It was our intention from the beginning to contribute to the solution of the web's censorship issues and becoming a bridge (or gateway) to the Web3.
|
||||
|
||||
|
|
@ -1,6 +1,44 @@
|
|||
---
|
||||
title: How it works
|
||||
title: Lume
|
||||
---
|
||||
|
||||
Since we defined the limitations of Web2 and building blocks of Web3, let's take a look at what Lume is and where it fits in the grander scale.
|
||||
|
||||
### How did it start
|
||||
|
||||
Lume started (before we even decided it was a project or the name) while we were trying to create a web3 cloud drive on Nextcloud based on Skynet. We realized that we were going down the wrong path and needed to solve accessing content before doing anything with the content itself.
|
||||
|
||||
Skynet in the process had a very rough year, as since 2020, Skynet tried to solve distribution with network of Skynet Portals, but experienced number of obstacles from all levels of internet infrastructure (see [Limitations of Web2](web2-limits.md)) and eventually was shut down.
|
||||
|
||||
Sia in the background was trying to support both innovating and Skynets efforts, and things came to a head with Skynet going bankrupt.
|
||||
|
||||
In that journey, Lume has pivoted at-least 1 time to meet its goals, and has ended up having to build many building blocks out of necessity, and a few that may go unused 🙃.
|
||||
|
||||
Sia has since started rebuilding with new software, and Lume has been building on top.
|
||||
|
||||
Sia is the network of the worlds data, and Handshake replaces ICANN while collaborating with the web3 ecosystem. We have discussed Sia a lot so far, but let it also be known the Handshake tribe has had its own share of drama too, and Lume is actively involved in both.
|
||||
|
||||
So the rabbit hole of Web3 DNS is where we started as the origin of Lume, which means the `world` or `light` in Romanian. It was our intention from the beginning to contribute to the solution of the web's censorship issues and becoming a bridge (or gateway) to the Web3.
|
||||
|
||||
|
||||
### What is Lume? Simple version, please!
|
||||
|
||||
`What is Lume?` This is something we have often asked ourselves to explain it 😅.
|
||||
|
||||
Lume can be broken down into a few major focuses:
|
||||
|
||||
- Lume is a **P2P network** that uses public keys instead of torrent hashes to access peers and content.
|
||||
- Like a BitTorrent, but ready for Web3. You can also see it to be a bit like IPFS which uses Libp2p, but more light weight.
|
||||
- The goal here is to create a bridge P2P network `to service all of Web3`.
|
||||
- `It's NOT a blockchain`. You don't need one since anyone can provide services with RPC or their own custom protocol, and anyone can query them.
|
||||
- Lume is a **storage portal** (think `L2` in blockchain terms).
|
||||
- It builds on Sia and stores your private data, and eventually public. In other words think of it like a paid IPFS service, but its not IPFS.
|
||||
- Lume is the **end user gateway**.
|
||||
- It is how you will interface with all content networks, blockchains, or other nets in the future. This could be a browser extension, web browser itself or anything in-between.
|
||||
|
||||
### Ok, I get it. Now how it works under the hood?
|
||||
|
||||
|
||||
#### It's a bridge, it's a gateway
|
||||
Lume can be seen as a middleware system where you can plug anything in and access it over the relay network. This is done with a help of Hypercore/Dat (see https://docs.holepunch.to which is born from https://dat-ecosystem.org) that allows it to proxy (relay) access to other networks anonymously, and to provide some DNS services. It is also end-to-end encrypted (based on https://noiseprotocol.org).
|
||||
|
||||
|
|
@ -22,6 +60,7 @@ This is the basis of how you can run light clients, SPV nodes, DNS resolvers, co
|
|||
|
||||
With blake3 we can also support real time verified streaming, which means files get verified based on their hash as you download so everything is fully trustless. See https://github.com/n0-computer/abao.
|
||||
|
||||
|
||||
#### Path forward
|
||||
|
||||
This browser tech can take many forms and Lume will continue evolving to be more advanced over time with its browsing abilities and more importantly, become easy and comfortable to use. That's its biggest problem today and also a reason we already started planning an extension for the most popular browser, Chrome. The end goal is a browser fork, but right now we need to get the foundations right.
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
title: Roadmap
|
||||
---
|
||||
|
||||
The following is our currently planned roadmap:
|
||||
|
||||
## 2024
|
||||
|
||||
| Quarter | Focus Area | Activities |
|
||||
|---------|--------------------------------------------------------|------------|
|
||||
| Q1 | Streamlining Code and Systems | <ul><li>🔄 <strong>Rewrite portal software</strong> for better maintenance and protocol support.</li><li>🔧 <strong>Refactor relay software</strong> using Bun.js and comlink.</li><li>📡 <strong>Redesign kernel software</strong> to simplify communication protocols.</li></ul> |
|
||||
| Q2 | Portal Dashboard, Billing, Marketing, and File Syncing | <ul><li>💻 <strong>Launch a user-friendly portal dashboard.</strong></li><li>🌐 <strong>Develop a portal marketing website.</strong></li><li>📣 <strong>Collect user feedback</strong> for portal dashboard and portal website improvements.</li><li>💳 <strong>Integrate billing functionality</strong> with Stripe to portal.</li><li>🔄 <strong>Enable file metadata sharing</strong> between portals using Hypercore.</li></ul> |
|
||||
| Q3 | Platform Upgrades and App Development | <ul><li>📰 <strong>Update web3.news</strong> to align with new infrastructure.</li><li>🎮 <strong>Upgrade features</strong> in web3browser.io and web3toybox.com demos.</li><li>🌍 <strong>Develop a browser extension</strong> and cross-platform web3 proxy app combo.</li></ul> |
|
||||
| Q4 | IPFS Integration, Hosting Launch, and Community | <ul><li>🌐 <strong>Integrate IPFS support</strong> into the portal.</li><li>🖥️ <strong>Prepare project hosting</strong> for production.</li><li>📰 <strong>Enhance and expand web3.news.</strong></li><li>🛠️ <strong>Diversify web3.news integrations</strong> with static site builders and create starter projects.</li></ul> |
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
title: Limitations of Web2
|
||||
---
|
||||
|
||||
**Currently, Web2 is a combination of multiple open protocols**.
|
||||
Currently, Web2 is a combination of multiple open protocols.
|
||||
- `HTTP (HyperText Transfer Protocol)` - used for transmission of information across the internet
|
||||
- `FTP (File Transfer Protocol)` - used to transfer files from a server to client
|
||||
- `SMTP (Simple Mail Transfer Protocol)` - used to send mail messages
|
||||
|
|
@ -16,7 +16,7 @@ You can also find a lot more limitations when you zoom out a bit and focus on ne
|
|||
|
||||
But most important of all is `Censorship`. With web content, nearly every single layer of the system has been captured and has the power to shut you down if scaring you with warnings is not enough.
|
||||
|
||||
**Let's look at censorship related infrastructure**:
|
||||
Let's look at those:
|
||||
- `ICANN` - A giant phone book hierarchy you can see as a group of database records knowns as `Domains`. This exists because people remember words better than numbers or codes and it is what makes market with domains so valuable. And while ICANN was originally founded by the government to be later made independent, it still can be corrupted and a subject to political pressure which makes it centralized and makes the criteria for getting new TLD's very difficult.
|
||||
- `DNS` - Your DNS providers can easily censor you or refuse to provide service. And even if they are a good one, they can be pressured or enforced todo the same. So what can you do if this happens to you? Not much - your one and only option is to move to other provider. And if they are your domain registrar at the same time, well...
|
||||
- `Hosting` - Your servers can be shut down any moment. There is a hierarchy and `ISP (Internet Service Provider)` has this right as a business partner too. If any of them or the government doesn't like what's going on, the pressure is applied and can go all the way up, shutting you down quickly or facing the consequences.
|
||||
|
|
@ -10,7 +10,7 @@ You can actually translate a lot of the Web2 technologies and components to thei
|
|||
|
||||
When you look at the marketing for the hundreds of Web3/DeFi projects, it's all full of strong claims and promises, every single project sounds like re-definition of the internet, while it actually is just begging for attention and your money.
|
||||
|
||||
So instead of trying to explain what Web3 involves, **lets explain what we have in Web2, and what its counterparts can look like in web3**.
|
||||
So instead of trying to explain what Web3 involves, lets explain what we have in Web2, and what its counterparts can look like in web3.
|
||||
|
||||
| Web2 Concept | Web3 Concept | Description |
|
||||
|----------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "@lumeweb/docs.lumeweb.com",
|
||||
"version": "0.3.0-develop.4",
|
||||
"version": "0.3.0",
|
||||
"private": true,
|
||||
"repository": {
|
||||
"type": "git",
|
||||
|
|
|
|||
28
sidebars.js
28
sidebars.js
|
|
@ -15,29 +15,11 @@
|
|||
const sidebars = {
|
||||
main: [
|
||||
"index",
|
||||
{
|
||||
type: "category",
|
||||
label: "Introduction",
|
||||
link: null,
|
||||
items: ["intro/about", "intro/components", "intro/history"],
|
||||
},
|
||||
{
|
||||
type: "category",
|
||||
label: "Problems We Are Solving",
|
||||
link: null,
|
||||
items: [
|
||||
"problems/better-web",
|
||||
"problems/web2-limits",
|
||||
"problems/web3-building-blocks",
|
||||
],
|
||||
},
|
||||
{
|
||||
type: "category",
|
||||
label: "Apps",
|
||||
link: null,
|
||||
items: ["apps/browser-webapp"],
|
||||
},
|
||||
"roadmap",
|
||||
"better-web",
|
||||
"web2-limits",
|
||||
"web3-building-blocks",
|
||||
"lume",
|
||||
"browser-webapp",
|
||||
],
|
||||
};
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +0,0 @@
|
|||
/better-web /problems/better-web
|
||||
/web2-limits /problems/web2-limits
|
||||
/web3-building-blocks /problems/web3-building-blocks
|
||||
/lume /intro/about
|
||||
/browser-webapp /apps/browser-webapp
|
||||
|
||||
|
||||
/better-web/ /problems/better-web
|
||||
/web2-limits/ /problems/web2-limits
|
||||
/web3-building-blocks/ /problems/web3-building-blocks
|
||||
/lume/ /intro/about
|
||||
/browser-webapp/ /apps/browser-webapp
|
||||
Loading…
Reference in New Issue