remove old tea party and wallet

tearust · Dec 20, 2023 · 99e14ab · 99e14ab
1 parent 09ddb47
commit 99e14ab
Show file tree

Hide file tree

Showing 10 changed files with 6 additions and 197 deletions.
diff --git a/docs/_1_ecosystem/2_example-tea-in-use.md b/docs/_1_ecosystem/2_example-tea-in-use.md
@@ -8,7 +8,7 @@ However, due to the lack of a central server, financial transactions between inv
 
 If we consider blockchain as layer-1, the TEA project as the layer-2 on blockchain, we may call the payment channel as layer-3. 
 
-[ TEA Party](../_5_tapps/TApp-TEA-Party.md) is the example app to demonstrate this feature.
+[ TEA Party](../_2_user_manual/_8_Tea%20Party.md) is the example app to demonstrate this feature.
 
 TEA Party allows a host(who create a video chat room, such as a teacher in classroom), get **paid per minute** by the guests(who are invited by the host via a shared URL link, such as students). There is no central server between host and guests. No matter how long the video chat does, there will be only two (or maybe three) payment transactions sent to the TEA Project network at the beginning and ending. Every minute (depending on cost structure set by the host) both host and guests exchange signed payment confirmation messages through the peer to peer network directly. The payment channel algorithm protect both sides from irresponsible behavior or incidentally network disconnection. 
 

diff --git a/docs/_1_ecosystem/4_tea-technical-details.md b/docs/_1_ecosystem/4_tea-technical-details.md
@@ -49,7 +49,7 @@ We aim to establish the TEA Project as the preferred development platform for de
 
 ### Peer to peer application architecture
 
-Besides typical three-tier applications, peer-to-peer applications are popular in the Web3 world. These applications are designed to be fully self-contained, which means almost all logic runs inside the client as a so-called "protocol". Therefore, they involve very little or zero server-side support. TEA Project fully supports this type of new Web3-oriented application architecture. TEA Project has integrated the **payment channel** protocol, which is similar to BTC's **Lightning Network**. Use WebRTC-based  [TEA Party example](../_5_tapps/TApp-TEA-Party.md) as an example, the only two server-involved places the host peer or guests' peers are 1. signaling (peers discovery) 2. payment channel setup & settlement. All the video/audio data is transferred between the host peer and guests' peers directly. In case the TEA Party hosting node is accidentally down during the call, none of the peers will notice, and their payment won't be affected.
+Besides typical three-tier applications, peer-to-peer applications are popular in the Web3 world. These applications are designed to be fully self-contained, which means almost all logic runs inside the client as a so-called "protocol". Therefore, they involve very little or zero server-side support. TEA Project fully supports this type of new Web3-oriented application architecture. TEA Project has integrated the **payment channel** protocol, which is similar to BTC's **Lightning Network**. Use WebRTC-based [TEA Party](../_2_user_manual/_8_Tea%20Party.md) as an example, the only two server-involved places the host peer or guests' peers are 1. signaling (peers discovery) 2. payment channel setup & settlement. All the video/audio data is transferred between the host peer and guests' peers directly. In case the TEA Party hosting node is accidentally down during the call, none of the peers will notice, and their payment won't be affected.
 
 ### Realtime collaborative application architecture
 

diff --git a/docs/_5_tapps/README.md b/docs/_5_tapps/README.md
@@ -7,7 +7,7 @@ From the end-users perspective, two steps are needed before deploying any TApp f
 1. A spending limit for the TApp must be set. This ensures that a TApp can't spend more than what you've allocated for that TApp. As money is spent in the TApp, the spending limit is reduced. In this way it functions like an allowance that can be spent, with the end-user able to bump it up at any time.
 1. A node must be selected to run the TApp. Because of TEA's architecture, TApps are "hosted" in IPFS waiting for deployment. Because IPFS is just storage, the node that the end-user requests will download the compiled TApp binary from IPFS and execute in the node together with any data that the end-user provides.
 
-The list of available TApps is available through the [TEA Browser Wallet](TEA-Browser-Wallet.md). 
+The list of available TApps is available through the [TAppStore](../_2_user_manual/_1_TAppStore_1_tapps.md).
 
 Developers interested in coding and deploying their own TApps can reference the following resources:
 
@@ -16,10 +16,3 @@ Developers interested in coding and deploying their own TApps can reference the
 * [TEA-Billing](TEA-Billing.md) is the base document with information and related links for understanding TEA's billing system.
 
 You can learn more about other concepts involved with TApps by visiting the [TApps FAQ](FAQ-TApps.md). 
-
-## More Info on Specific TApps
-
-There's a [core set of TApps](TApps-Core.md) that are maintained by the team. These include
-
-* [The TEA Party TApp](TApp-TEA-Party.md). TEA Party is a social messaging app that's also useful for developers to study and learn from.
-* [The TEA Influencer TApp](TEAfluencer.md). TEAfluencer is a TApp template that can be used by any influencer to create their own faucet for the TEA ecosystem. 
diff --git a/docs/_5_tapps/TApp-TEA-Party.md b/docs/_5_tapps/TApp-TEA-Party.md
diff --git a/docs/_5_tapps/TEA-Browser-Wallet.md b/docs/_5_tapps/TEA-Browser-Wallet.md
diff --git a/obsidian/_1_ecosystem/2_example-tea-in-use.md b/obsidian/_1_ecosystem/2_example-tea-in-use.md
@@ -8,7 +8,7 @@ However, due to the lack of a central server, financial transactions between inv
 
 If we consider blockchain as layer-1, the TEA project as the layer-2 on blockchain, we may call the payment channel as layer-3. 
 
-[[TApp-TEA-Party| TEA Party]] is the example app to demonstrate this feature.
+[[_8_Tea Party| TEA Party]] is the example app to demonstrate this feature.
 
 TEA Party allows a host(who create a video chat room, such as a teacher in classroom), get **paid per minute** by the guests(who are invited by the host via a shared URL link, such as students). There is no central server between host and guests. No matter how long the video chat does, there will be only two (or maybe three) payment transactions sent to the TEA Project network at the beginning and ending. Every minute (depending on cost structure set by the host) both host and guests exchange signed payment confirmation messages through the peer to peer network directly. The payment channel algorithm protect both sides from irresponsible behavior or incidentally network disconnection. 
 

diff --git a/obsidian/_1_ecosystem/4_tea-technical-details.md b/obsidian/_1_ecosystem/4_tea-technical-details.md
@@ -50,7 +50,7 @@ We aim to establish the TEA Project as the preferred development platform for de
 
 ### Peer to peer application architecture
 
-Besides typical three-tier applications, peer-to-peer applications are popular in the Web3 world. These applications are designed to be fully self-contained, which means almost all logic runs inside the client as a so-called "protocol". Therefore, they involve very little or zero server-side support. TEA Project fully supports this type of new Web3-oriented application architecture. TEA Project has integrated the **payment channel** protocol, which is similar to BTC's **Lightning Network**. Use WebRTC-based  [[TApp-TEA-Party|TEA Party example]] as an example, the only two server-involved places the host peer or guests' peers are 1. signaling (peers discovery) 2. payment channel setup & settlement. All the video/audio data is transferred between the host peer and guests' peers directly. In case the TEA Party hosting node is accidentally down during the call, none of the peers will notice, and their payment won't be affected.
+Besides typical three-tier applications, peer-to-peer applications are popular in the Web3 world. These applications are designed to be fully self-contained, which means almost all logic runs inside the client as a so-called "protocol". Therefore, they involve very little or zero server-side support. TEA Project fully supports this type of new Web3-oriented application architecture. TEA Project has integrated the **payment channel** protocol, which is similar to BTC's **Lightning Network**. Use WebRTC-based [[_8_Tea Party|TEA Party]] as an example, the only two server-involved places the host peer or guests' peers are 1. signaling (peers discovery) 2. payment channel setup & settlement. All the video/audio data is transferred between the host peer and guests' peers directly. In case the TEA Party hosting node is accidentally down during the call, none of the peers will notice, and their payment won't be affected.
 
 ### Realtime collaborative application architecture
 

diff --git a/obsidian/_5_tapps/README.md b/obsidian/_5_tapps/README.md
@@ -7,7 +7,7 @@ From the end-users perspective, two steps are needed before deploying any TApp f
 1. A spending limit for the TApp must be set. This ensures that a TApp can't spend more than what you've allocated for that TApp. As money is spent in the TApp, the spending limit is reduced. In this way it functions like an allowance that can be spent, with the end-user able to bump it up at any time.
 2. A node must be selected to run the TApp. Because of TEA's architecture, TApps are "hosted" in IPFS waiting for deployment. Because IPFS is just storage, the node that the end-user requests will download the compiled TApp binary from IPFS and execute in the node together with any data that the end-user provides.
 
-The list of available TApps is available through the [TEA Browser Wallet](TEA-Browser-Wallet.md). 
+The list of available TApps is available through the [[_1_TAppStore_1_tapps|TAppStore]].
 
 Developers interested in coding and deploying their own TApps can reference the following resources:
 
@@ -17,9 +17,3 @@ Developers interested in coding and deploying their own TApps can reference the
 
 You can learn more about other concepts involved with TApps by visiting the [TApps FAQ](FAQ-TApps.md). 
 
-## More Info on Specific TApps
-There's a [core set of TApps](TApps-Core.md) that are maintained by the team. These include
-
-- [The TEA Party TApp](TApp-TEA-Party.md). TEA Party is a social messaging app that's also useful for developers to study and learn from.
-- [The TEA Influencer TApp](TEAfluencer.md). TEAfluencer is a TApp template that can be used by any influencer to create their own faucet for the TEA ecosystem. 
-