2024-05-11 17:44:33 +00:00
9 changed files with 15 additions and 84 deletions
--- a/books/duniayetu_dar/SUMMARY.md
+++ b/books/duniayetu_dar/SUMMARY.md
@ -23,10 +23,11 @@
    - [Clouds Are Complicated](problems/cd_issues_cloud_not_enough.md)
    - [Content Delivery is Expensive](problems/cd_issues_cost.md)
 - [Solutions](solutions/solutions.md)
-  - [Decentralized Cloud](solutions/cloud/cloud.md)
  - [Content Providers](solutions/content_providers/content_providers.md)
+  - [FreeFlow Self](web4/freeflowself/freeflowself.md)
+  - [Actor Based Development](web4/actor_based/actor_based_approach.md)
+  - [Vlang](web4/vlang/vlang.md)
      <!-- - [Social Media Platform]() -->
-  - [Web4](web4/web4.md)
 - [Farming](farming_v4/farming.md)
    - [TFNodes](farming_v4/tf_nodes.md)
    - [TFRouters](farming_v4/tf_routers.md)
@ -35,9 +36,4 @@
 - [Social Media Protocols](social_media_protocols/protocols.md)
     - [Nostr Protocol](social_media_protocols/nostr.md)
     - [Activity Pub](social_media_protocols/activitypub.md)
- [Technology](web4/web4.md)
-     - [FreeFlow Self](web4/freeflowself/freeflowself.md)
-     - [Actor Based Development](web4/actor_based/actor_based_approach.md)
-     - [Vlang](web4/vlang/vlang.md)
-
 <!-- - [FreeFlow Self](ffself_specs/freeflowself/freeflowself.md) -->
--- a/collections/farming_v4/tf_routers.md
+++ b/collections/farming_v4/tf_routers.md
@ -13,7 +13,7 @@ It's an exciting node with a reasonable price point and enough CPU capacity to r

 More than 1 node can be installed in a larger office, hotel, home, etc., and they will automatically mesh together.

-Each node runs our *ZNET Operating System, allowing for native integration into the TFGrid network.
+Each node runs our ZeroNet Operating System, allowing for native integration into the TFGrid network. This operating system allows to create distributed networking on a planetary scale and allows our farmers to provide network capacity to the grid ecosystem.

 Zero-OS Nodes are seamlessly integrated with the Zero-Net nodes by design, requiring minimal configuration. They are part of our Autonomous Zero-OS Stack.

--- a/collections/freeflow/community_principles/community_principles.md
+++ b/collections/freeflow/community_principles/community_principles.md
@ -1,14 +1,9 @@
-
-
 # FreeFlow Community Principles 

-> TODO: Page needs to be improved
-
 ## Inclusion

 ![](img/principles_01.png)

-
 “If not US, then who? If not NOW then when?” 

 Anyone may be a part of FreeFlowCommunity. We welcome and respect the stranger. No pre-requisites exist for participation in our community.
@ -66,7 +61,7 @@ We value civil society. Community members who organize events should assume resp

 "We return to Responsible Community Building"

-## Leave no Trace = Planet First
+## Leave No Trace = Planet First

 ![](img/principles_08_.jpg)

--- a/collections/problems/painkiller/cd_issues_cost.md
+++ b/collections/problems/painkiller/cd_issues_cost.md
@ -6,7 +6,7 @@
 - Other specialized CDN's can be around 10 per TB if services from e.g. Europe or US, smaller CDN's are much more expensive.
 - Managing these CDN's is expensive and not easy job.

->> This means to service 10m people, it would cost about 1 to 2m USD per month just for CDN alone.
+> This means to service 10m people, it would cost about 1 to 2m USD per month just for CDN alone.


 # CDN Pricing Amazon
--- a/collections/social_media_protocols/nostr.md
+++ b/collections/social_media_protocols/nostr.md
@ -32,11 +32,4 @@ Despite its innovative approach, it has several limitations:
 - **Resource Constraints**
    - Running a relay requires resources, and smaller entities or individuals may struggle to participate as relay operators due to these constraints.
 - **Interoperability and Standards**
-    - As Nostr is an evolving protocol, maintaining interoperability between different clients and adherence to standards is challenging, which could lead to fragmentation.
-
-<!-- todo: add technical remarks 
-## Our Technical Remarks
-
- ...
-
-->
+    - As Nostr is an evolving protocol, maintaining interoperability between different clients and adherence to standards is challenging, which could lead to fragmentation.
--- a/collections/solutions/content_providers/cdn_cost.md
+++ b/collections/solutions/content_providers/cdn_cost.md
@ -1,53 +0,0 @@
-![](img/cdn2.png)
-
-## high CDN cost = Content Delivery
-
- CDN's cost between 20 and 60 on major CDN's from Amazon, Google, ..., after negotiation and willingness to park lots of money and commit per month it mught be certain discount.
- Other specialized CDN's can be around 10 per TB if services from e.g. Europe or US, smaller CDN's are much more expensive.
- Managing these CDN's is expensive and not easy job.
-
->> this means to service 10m people it would cost about 1 to 2m USD per month just for CDN alone.
-
-
-# CDN pricing Amazon
-
-Remark no fees included for HTTPS requests, but should be ok for volume we are talking about, if app is made in right way.
-
-## US
-
-![](img/amz_us.png)
-
-= 28 USD per TB in US
-
-## EUR
-
-![](img/amz_eur.png)
-
-## MIDDLE EAST
-
-![](img/amz_middleeast.png)
-
-= 56 USD per TB
-
-## AFRICA
-
-![](img/amz_sa.png)
-
-= 56 USD per TB
-
-## Discounts
-
- discounts can be negotiated but required serious amounts of pre-financing
-
-# CDN pricing Google
-
-Remark no fees included for HTTPS requests, but should be ok for volume we are talking about, if app is made in right way.
-
-![](img/google_1.png)
-
-![](img/google2.png)
-
-https://cloud.google.com/cdn/pricing
-
-
-
--- a/collections/solutions/solutions.md
+++ b/collections/solutions/solutions.md
@ -0,0 +1,6 @@
+# Solutions
+
+- [Content Providers](solutions:content_providers.md)
+- [FreeFlow Self](web4:freeflowself.md)
+- [Actor Based Development](web4:actor_based_approach.md)
+- [Vlang](web4:vlang.md)
--- a/collections/web4/actor_based/actor_based_approach.md
+++ b/collections/web4/actor_based/actor_based_approach.md
@ -2,12 +2,8 @@

 ![](img/twin_model.png)

-'actor' driven pattern instead of a model first pattern. 
+We use an 'actor' driven pattern instead of a model first pattern. 

 In such a pattern, the root model only holds essentials in its database, hence any necessary changes can be applied at the root. 

-The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes. 
-
-> TODO: too dense, need more explanation
-
-
+The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes. 
--- a/collections/web4/freeflowself/freeflowself.md
+++ b/collections/web4/freeflowself/freeflowself.md
@ -9,8 +9,6 @@ FreeFlow Self is your unique digital "self" - in other worlds, it is you in this

 FreeFlow Self guarantees that only you have access to your data - no one else. It encourages a trustful environment without any manipulation attempt from third parties.

-> TODO: need more complete and easy to understand explanation, more practical
-
 ## Link to 3Bot

 3Bot is a first implementation of the FreeFlow Self, its rather technical and in heavy development at this stage.