Replying to Avatar btcdage

从WEB1.0到WEB4.0

by Btcdage

本文列举WEB1.0到WEB4.0(nostr)的特点及优缺点,聊以抛砖引玉。

【WEB1.0】

BS架构,B为浏览器客户端,S为服务器端。

1、所有数据由平台所有者发布在服务器中,用户只能通过浏览器被动接受服务器返回的数据。

2、数据产权完全归平台所有者,平台所有者(服务器管理员)拥有数据的全部增删改的权限。

缺点:数据采集缺乏用户参与

【WEB 2.0】

BS架构,B为浏览器或者APP“客户端”,S为“服务器端”。

1、数据可由用户进行发布,数据存放在平台所有者的中心服务器(或集群)中。

2、用户通过账户和口令进行平台登录,所有账户数据包括口令(有可能加密过)等敏感信息也存放在平台

3、所有者的中心服务器(或集群)中。不同的平台需要分别注册账户,用户信息不能跨平台使用。

4、用户数据产权完全归平台所有者,平台所有者有权对用户账户的权限进行限制甚至封禁,也可对用户数据进行修改或删除。

进步:用户深度参与数据的采集

缺点:用户无法保护对自己数据的权利,任由平台方处置。平台自身也容易被铁拳限制或者关闭。

【WEB 3.0】

BS架构,B为浏览器或者APP访问的“DAPP”,S为“区块链”。

1、数据由用户进行发布,数据存放在区块链中(不考虑毫无意义的非公链)。

2、用户通过加密学,根据公链的不同使用相应的不对称加密算法,使用公钥(地址)作为账户ID,私钥作为签名凭据。用户私钥不保存在任何服务器中。同一类型的公链的“用户账户”通用(比如ETH/BSC/OKC/KSC通用,不能跨异类型的公链),但是用户其他数据只保存在平台方使用的单独链上,无法跨链使用。

3、虽然理想状态的公链,元数据无法修改或删除。但通过智能合约,平台方实际控制了用户数据的指针。另外智能合约的版本升级也完全由平台方控制。用户对自己的数据仍然没有真正的权利。

进步:不再使用用户密码进行账户鉴权,私钥由用户独自控制,独立性、安全性、隐私性得到极大提升。

缺点:数据仍由平台方实际控制,通过智能合约,平台方仍然可以对用户进行限制甚至封禁。

【nostr协议(WEB 4.0)】

BS架构,B为浏览器或者APP访问的“客户端”,S为“中继器”。

1、数据由用户进行发布,数据存储在任意数量的中继器中。

2、用户通过统一的不对称加密算法,使用公钥作为账户ID,私钥作为签名凭据,实现对身份和操作的鉴权。这种账户鉴权发生在客户端,是通用且与中继器无关的。

3、每个中继器的管理员只能对自己架设的中继器的数据进行裁剪操作(只能删不能改,因为修改数据需要私钥签名,篡改的数据会被客户端丢弃)。虽然中继器之间不会自动同步,但由于客户端同时连接若干中继器,可以同时发布数据到这些中继器中。读取也是同时读取若干个中继器。因此,一部分中继器的用户数据被删除不影响用户的使用。任何一个中继器的管理员都无法实现封禁某个用户数据(无论是账户信息还是发布的数据)。

4、中继器很容易搭建,任何人都可以搭建一个自己的中继器来实现自己的数据副本。加强了去中心化,确保第三点的实现。

进步:

1、用户账户完全由加密学生成,且所有平台通用,在互联网上第一次实现了“用户实际意义拥有自己账户数据的权利”。

2、用户去中心化,由于第一点的进步,用户数据第一次完全跨平台,不同的平台客户端访问同样的一批中继器,返回的数据完全一致。

3、客户端的去中心化,只要是按照nostr协议开发的客户端,就可以从中继器读取数据,比如iris和astral是不同的客户端,但是读取的数据是一样的。使用户不再担心平台被铁拳制裁——一个客户端站点访问不了换一个就是。如果客户端做成应用程序或app,就更彻底的去中心化了。

3、中继器的去中心化,使得权力无法完全封禁数据源,提高了数据的鲁棒性。

在nostr协议下:

1、中继器管理员拥有自己中继器的完全权利,但是无法干涉用户权利。

2、用户掌控自己数据的完全权利,但是无法干涉某一个中继器管理员的权利。

3、应用平台的企业家可以根据自己的判断,在自己发布客户端时,在客户端侧对数据进行审查和筛选,也可以添加广告和其他业务,但是无法干涉用户是否选择采用其他客户端去访问中继器的权利,也无法干涉其他人建立的中继器的管理权。

人人管好属于自己产权的事情,没有权力干涉他人权利。自己的任何行为的结果交给市场。

这就是nostr协议的哲学思想,也是其有资格可以称之为未来的WEB4.0的重要原因。

From WEB1.0 to WEB4.0

by Btcdage

This article lists the characteristics and advantages and disadvantages of WEB1.0 to WEB4.0 (nostr), and chats with others.

【WEB1.0】

BS architecture, B is the browser client, S is the server.

1. All data is published on the server by the platform owner, and users can only passively accept the data returned by the server through the browser.

2. The property rights of the data belong entirely to the platform owner, and the platform owner (server administrator) has the authority to add, delete, and modify all data.

Cons: Lack of user involvement in data collection

【WEB 2.0】

BS architecture, B is the browser or APP "client", S is the "server".

1. Data can be published by users, and the data is stored in the central server (or cluster) of the platform owner.

2. Users log in to the platform through their accounts and passwords, and all account data including passwords (which may be encrypted) and other sensitive information are also stored on the platform

3. In the owner's central server (or cluster). Different platforms need to register accounts separately, and user information cannot be used across platforms.

4. The property rights of user data belong entirely to the platform owner, and the platform owner has the right to restrict or even ban user account permissions, as well as modify or delete user data.

Progress: Users are deeply involved in the collection of data

Disadvantage: Users cannot protect their rights to their own data and let the platform handle it. The platform itself is also easily restricted or shut down by Iron Fist.

【WEB 3.0】

BS architecture, B is the "DAPP" accessed by the browser or APP, and S is the "blockchain".

1. The data is published by the user, and the data is stored in the blockchain (regardless of meaningless non-public chains).

2. Through cryptography, the user uses the corresponding asymmetric encryption algorithm according to the difference of the public chain, uses the public key (address) as the account ID, and the private key as the signature credential. User private keys are not stored in any server. The "user account" of the same type of public chain is common (for example, ETH/BSC/OKC/KSC are common, and cannot cross public chains of different types), but other user data are only stored on a separate chain used by the platform, and cannot be used across chains .

3. Although the public chain is in an ideal state, the metadata cannot be modified or deleted. But through the smart contract, the platform side actually controls the user data pointer. In addition, the version upgrade of the smart contract is completely controlled by the platform side. Users still have no real rights over their own data.

Progress: User passwords are no longer used for account authentication, private keys are controlled by users alone, and independence, security, and privacy have been greatly improved.

Disadvantages: The data is still actually controlled by the platform side. Through smart contracts, the platform side can still restrict or even ban users.

[nostr protocol (WEB 4.0)]

BS architecture, B is the "client" accessed by the browser or APP, and S is the "repeater".

1. The data is published by the user, and the data is stored in any number of repeaters.

2. Through a unified asymmetric encryption algorithm, the user uses the public key as the account ID and the private key as the signature credential to authenticate identity and operations. This account authentication happens on the client side and is generic and independent of the relayer.

3. The administrator of each repeater can only trim the data of the repeater set up by itself (it can only be deleted but not modified, because the modification of the data requires a private key signature, and the tampered data will be discarded by the client). Although there is no automatic synchronization between repeaters, since the client connects to several repeaters at the same time, it can publish data to these repeaters at the same time. Reading is also reading several repeaters at the same time. Therefore, the deletion of user data of some repeaters will not affect the use of users. The administrator of any repeater cannot ban a user's data (whether it is account information or published data).

4. Repeaters are easy to build, and anyone can build their own repeater to realize their own data copy. Strengthened decentralization to ensure the realization of the third point.

progress:

1. User accounts are completely generated by encryption, and all platforms are common. For the first time on the Internet, "users have the right to actually own their own account data".

2. User decentralization. Due to the progress of the first point, user data is completely cross-platform for the first time. Different platform clients access the same batch of repeaters, and the returned data is exactly the same.

3. Decentralization of the client, as long as the client is developed according to the nostr protocol, it can read data from the repeater. For example, iris and astral are different clients, but the read data is the same. So that users no longer worry about the platform being sanctioned by an iron fist - if one client site cannot be accessed, another one will be replaced. If the client is made into an application or app, it will be more completely decentralized.

3. The decentralization of repeaters makes it impossible for power to completely block data sources, improving the robustness of data.

Under the nostr agreement:

1. Repeater administrators have full rights to their own repeaters, but cannot interfere with user rights.

2. Users have complete rights to control their own data, but cannot interfere with the rights of a repeater administrator.

3. Entrepreneurs of the application platform can review and screen the data on the client side when they release the client according to their own judgment, and can also add advertisements and other services, but they cannot interfere with whether the user chooses to use other clients to The right to access the relay, and cannot interfere with the management of the relay established by others.

Everyone manages the things that belong to their own property rights, and has no right to interfere with the rights of others. The results of any of your actions are handed over to the market.

This is the philosophy of the nostr protocol, and it is also an important reason why it is qualified to be called the future WEB4.0.

Reply to this note

Please Login to reply.

Discussion

No replies yet.