...

.gitignore

@@ -1,23 +0,0 @@
-# Dependencies
-/node_modules
-
-# Production
-/build
-
-# Generated files
-.docusaurus
-.cache-loader
-
-# Misc
-.DS_Store
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-bun.lockb
-
-yarn.lock

LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2024 ThreeFold.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

README.md

@@ -1,37 +1 @@
-<h1>ThreeFold Tech Website</h1>
+everything moved to tech dir in docs_tfgrid4
-
-<h2>Table of Contents</h2>
-
-- [Introduction](#introduction)
-- [Steps](#steps)
-- [URL](#url)
-
----
-
-## Introduction
-
-This repository contains the code to deploy the ThreeFold Tech website.
-
-## Steps
-
-- Install
-    ```
-    bash install.sh
-    ```
-- Run locally
-    ```
-    bash develop.sh
-    ```
-- Push change online to stating website
-    ```
-    bash build-dev.sh
-    ```
-- Push change online to production website
-    ```
-    bash build.sh
-    ```
-
-## URL
-
-- The website in staging mode is at `threefold.info/tftechdev`
-- The website in production mode is at `threefold.info/tftech`

build-dev.sh

@@ -1,20 +0,0 @@
-#!/bin/bash
-
-set -ex
-
-script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-cd "${script_dir}"
-
-export PATH=${BASE}/node_modules/.bin:$PATH
-
-echo "Docs directory: $script_dir"
-
-# Change baseUrl to '/tftechdev/'
-sed -i "s|/tftech/|/tftechdev/|g" docusaurus.config.ts ./src/pages/index.tsx
-
-bun docusaurus build
-
-rsync -rv --delete ${script_dir}/build/ root@info.ourworld.tf:/root/hero/www/info/tftechdev
-
-# Change baseUrl to '/tftech/'
-sed -i "s|/tftechdev/|/tftech/|g" docusaurus.config.ts ./src/pages/index.tsx

build.sh

@@ -1,14 +0,0 @@
-#!/bin/bash
-
-set -ex
-
-script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-cd "${script_dir}"
-
-export PATH=${BASE}/node_modules/.bin:$PATH
-
-echo "Docs directory: $script_dir"
-
-bun docusaurus build
-
-rsync -rv --delete ${script_dir}/build/ root@info.ourworld.tf:/root/hero/www/info/tftech

develop.sh

@@ -1,14 +0,0 @@
-#!/bin/bash
-
-set -ex
-
-script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-cd "${script_dir}"
-
-echo "Docs directory: $script_dir"
-
-#export NODE_OPTIONS=--openssl-legacy-provider
-
-#npm run start -- --host 0.0.0.0
-
-bun run start -p 3100

docs/main/first_principle_thinking/1_onion_analogy.md

@@ -1,48 +0,0 @@
----
-title: 'Avoid Painkillers'
-sidebar_position: 2
----
-
-![](img/onion.png)
-
-> First principles thinking is a problem-solving method that involves breaking down a problem into its most basic parts and then rebuilding it from the ground up
-
-# The Onion Analogy
-
-Most cloud & internet stacks can be compared to an onion, where each layer represents an additional component or service added to address a problem in the system. However, like peeling an onion, as you dig deeper, you often find that these layers are not solving the core issues but merely masking symptoms, leading to a complex and often fragile structure.
-
-## Quick Fixes and Additions
-
-- **Problem:** When an issue arises, such as performance bottlenecks or security vulnerabilities, organizations often add another tool, service, or layer to the cloud stack to mitigate the issue.
-- **Analogy:** This is akin to applying a bandage or taking a painkiller when you feel pain. The immediate discomfort might be alleviated, but the underlying problem remains untouched.
-
-## Painkiller Approach: Treating Symptoms, Not Causes
-
-This onion-like structure represents a "painkiller approach" to cloud management, where immediate issues are addressed with quick fixes rather than tackling the underlying problems. Over time, this approach leads to several challenges.
-
-This onion-like structure represents a "painkiller approach" to cloud management, where immediate issues are addressed with quick fixes rather than tackling the underlying problems. 
-
-Over time, this approach leads to several challenges:
-
-- **Cyber Pandemic** The Cyber Pandemic is real, added these layers leads to weak security.
-- **Increased Complexity:** Each new layer adds complexity, making the system harder to understand and maintain.
-- **Higher Costs:** More layers often mean more resources, licenses, and management overhead, increasing operational costs.
-- **Reduced Agility:** The more complex the stack, the harder it is to make changes or adapt to new requirements, reducing the system’s overall agility.
-- **Fragility:** A stack built on temporary fixes is more prone to failures because the core issues are not resolved, making the system brittle.
-
-### We cannot solve our problems with the same thinking we used when we created them
-
-
-This is a famous quote by Einstein that we deeply admire.
-Here are a few others that we strive to live by.
-
----------
-
-"If I had an hour to solve a problem, I would spend 55 minutes thinking about the problem and 5 minutes thinking about solutions."
-
----------
-
-"Everything should be made as simple as possible, but not simpler."
-
-
-

docs/main/first_principle_thinking/2_hardware_badly_used.md

@@ -1,105 +0,0 @@
----
-title: 'Hardware Is Powerful'
-sidebar_position: 6
-hide_title: true
----
-
-# Hardware Is Powerful
-
-![](img/hardware_comparison.png)
-
-
-### The IT world fails to harness the full potential of computer hardware.
-
-
-While hardware advancements have surged forward, user experiences and features have often stagnated, failing to keep pace with these developments.
-
-The original Commodore 64, with only 64 KB of memory, was a remarkably capable machine for its time. In contrast, today's computers have 8 GB or more of memory, yet their capabilities have not necessarily improved proportionately.
-
-This highlights a regression in our ability to fully utilize computer hardware.
-
-We are committed to bridging this gap by optimizing our approach to hardware utilization, thereby unlocking its full potential. 
-
-## Why Are Servers So Badly Used?
-
-![](img/layers.png)
-
-Context switches occur when a computer's processor shifts from executing one task (or context) to another. While necessary for multitasking, too many context switches lead to inefficiency, as demonstrated in this diagram. Below, we provide a simplified explanation.
-
-## Why Context Switches Are a Problem
-
-### What Are Context Switches?
-
-Imagine you're working on two tasks: reading a book and answering emails. Every time you switch between them, you lose time refocusing. Computers experience a similar "refocusing" delay when switching between tasks.
-
-### The Layered Architecture Causes Overhead
-
-Modern computing systems use many layers (e.g., applications, storage drivers, network layers) to get work done. Each layer requires the system to switch between different modes (user mode and kernel mode) and tasks.
-
-For example:
-
-  - A web app might need to talk to a storage driver.
-  - This requires moving data through multiple layers (network, file system, etc.).
-  - Each layer adds a context switch.
-
-### Millions of Switches Per Second
-
-Each switch requires saving and loading the state of a process. This takes time and uses CPU power. When millions of context switches occur every second (as shown in the diagram), most of the computer’s capacity is spent switching rather than doing useful work.
-
-### Result: Wasted Resources
-   
-- Sometimes up to 90% of the computer’s capacity can be lost because of this inefficiency.
-- Instead of performing tasks like running applications or processing data, the computer is stuck managing unnecessary complexity.
-
-
-## Simplified Analogy
-
-Imagine driving on a highway where you have to stop and pay a toll at every intersection. You waste more time paying tolls than actually driving to your destination. Similarly, excessive context switches in modern systems cause the computer to "stop and pay tolls" constantly, leaving little time for real work.
-
-
-## How Did We Get Here
-
-![](img/eng_model_failing.png)
-
-
-## How to Resolve This Problem
-
-We decided to reinvent the way an operating system functions in a cloud and data center context.
-While leveraging the Linux kernel, we rebuilt many surrounding tools to minimize complexity and reduce context switching.
-This approach results in significantly improved security, scalability, and sustainability.
-
-> [See here for more information about our operating system called Zero-OS](../key_innovations_overview/cloud/compute/zos_compute.md)
-
-### Context Switching Details 
-
-In the context of CPU scheduling in Linux (and in most modern operating systems), a context switch refers to the process of saving the state of a currently running process (such as its registers, program counter, and other relevant information) and loading the state of a different process to allow it to run. This switching of execution from one process to another is a fundamental aspect of multitasking operating systems, where multiple processes share the CPU's time.
-
-### How It Works
-
-Here's how a context switch typically works in Linux:
-
-1. **Interrupt Handling**: When a higher-priority process needs to run or an event requiring immediate attention occurs (such as I/O completion), the CPU interrupts the currently running process.
-
-2. **Saving Context**: The operating system saves the state of the current process, including its registers, program counter, and other relevant data, into its process control block (PCB). This step ensures that when the process resumes execution later, it can continue from where it left off.
-
-3. **Scheduling Decision**: The operating system scheduler determines which process should run next based on scheduling algorithms and the priority of processes in the system.
-
-4. **Loading Context**: The operating system loads the state of the selected process from its PCB into the CPU, allowing it to execute. This includes restoring the process's registers, program counter, and other relevant data.
-
-5. **Execution**: The newly loaded process begins executing on the CPU.
-
-### Overhead and Performance Impact
-
-Context switches are essential for multitasking, but they come with overhead that can impact system performance:
-
-1. **Time Overhead**: Context switches require time to save and restore process states, as well as to perform scheduling decisions. This overhead adds up, especially in systems with many processes frequently switching contexts.
-
-2. **Cache Invalidation**: Each time a process is switched in, it may result in cache invalidation, where the CPU's cache needs to be refreshed with data from the new process's memory space. This can lead to cache misses and performance degradation.
-
-3. **Resource Contentions**: Context switches can exacerbate resource contention issues, especially in systems with limited CPU cores. If multiple processes are frequently contending for CPU time, the overhead of context switches can further delay process execution.
-
-4. **Fragmentation**: Frequent context switches can lead to memory fragmentation, as processes are loaded and unloaded into memory. This fragmentation can degrade system performance over time, as it becomes more challenging to find contiguous slice of memory for new processes.
-
-While context switches are necessary for multitasking, excessive context switching can indeed lead to a significant loss of execution power by introducing overhead and resource contention in the system. 
-
-Therefore, efficient scheduling algorithms and optimization techniques are crucial for minimizing the impact of context switches on system performance.

docs/main/first_principle_thinking/3_internet_risk.md

@@ -1,112 +0,0 @@
----
-title: 'Internet Protocol Upgrade'
-sidebar_position: 6
----
-
-![](img/tcpip.png)
-
-The foundational protocols of the internet, TCP/IP (Transmission Control Protocol/Internet Protocol), were created in the 1970s to connect a few academic and military computers. While they served their initial purpose, they were never designed for the complex, global, and interconnected world we live in today. Even IPv6, which addresses some scalability issues, does not solve the fundamental design flaws. 
-
-
-### How the Internet is Broken Due to TCP/IP Design
-
-The internet, as we know it today, is built on an outdated foundation that was designed for simpler times. Decades ago, TCP/IP was created to connect a handful of computers for research and military purposes. It worked well back then, but it’s no longer enough to handle the complexities of our modern, globally interconnected world. Unless we address its flaws, the internet will struggle to keep up—and could ultimately fail us.
-
-One major issue is that the internet has no way of "remembering" conversations. For example, when you watch a video or make a video call, your device creates a session—a temporary connection with another server. If this session is interrupted, the entire connection breaks, and you must start over. TCP/IP wasn’t designed to manage sessions, making it unreliable for modern apps and services that depend on continuous communication.
-
-Another problem is the internet’s complexity. The way it works involves layers of technology stacked on top of each other—apps, storage systems, networks, and more. These layers often don’t communicate efficiently, wasting resources and making everything slower, more expensive, and harder to fix. This complexity also makes the internet fragile, as small issues can cascade into larger failures.
-
-Security is another area where TCP/IP falls short. It wasn’t designed with cybersecurity in mind, which is why we rely on add-ons like firewalls, VPNs, and encryption. But these tools are essentially patches over a flawed system, and they add even more complexity, making the internet less robust and more vulnerable to attacks.
-
-Modern services and devices have also outgrown the static design of TCP/IP. The system assumes that servers and devices stay in fixed locations, but today’s internet is dynamic. Cloud services, mobile devices, and apps often move across networks. This static model creates inefficiencies and slows down the system.
-
-Adding to the problem is the internet’s dependence on a few centralized services, such as Google, Amazon, and Microsoft. These companies control much of the infrastructure we rely on for communication, storage, and services. If one of them fails—or if access is blocked due to political conflicts—entire regions can lose critical internet functions. This centralization makes the system fragile and leaves users vulnerable.
-
-> The stakes are high. The internet is essential for communication, education, business, and so much more. Yet its foundation is crumbling under modern demands. Without major changes, we’ll see more frequent failures, slower services, and increased vulnerabilities. In extreme cases, parts of the internet could break entirely.
-
-To fix this, we need a smarter, more resilient approach. Decentralized networks can distribute resources and reduce our dependence on a few central providers. Emerging technologies like RINA (Recursive Inter-Network Architecture) offer a simplified, more secure, and more efficient alternative to TCP/IP. These systems are designed to handle the needs of the modern internet, with built-in reliability, smarter communication, and security at their core.
-
-> The bottom line is clear: the internet’s outdated foundation is holding us back. If we want the internet to remain reliable and serve future generations, we must address these issues now. A decentralized, secure, and modernized internet isn’t just a technical upgrade—it’s a necessity for our connected world.
-
-
-## Tech Brief
-
-The following tech brief is aimed at experts.
-
-### 1. **Lack of Session Management**
-- **TCP/IP’s Shortcomings**
-  - TCP/IP lacks true session management. A session represents an ongoing communication between two entities (e.g., a user browsing a website). If the connection is interrupted (e.g., due to a network outage or device change), the session is lost, and applications must restart or recover manually.
-  - This flaw creates inefficiencies in modern applications that require reliable, continuous communication, such as video calls, gaming, or IoT devices.
-
-- **Why It Matters**
-  - Every time a session breaks, applications have to rebuild connections at a higher level (e.g., re-authenticate or restart a video call). This is inefficient and increases complexity, making the internet fragile and less resilient.
-
-
----
-
-### 2. **Layer Violations**
-
-- **The Problem**
-  - TCP/IP combines different functionalities into a single stack, leading to inefficiencies. For example:
-    - Routing decisions happen at the IP layer.
-    - Reliable data transfer happens at the TCP layer.
-  - However, these layers are not isolated and often interfere with each other, creating unnecessary overhead.
-
-- **Impact**
-  - Modern networks require additional layers (e.g., firewalls, VPNs, NATs) to patch these issues, making the architecture increasingly complex and brittle.
-
----
-
-### 3. **No Built-In Security**
-- **TCP/IP Design Flaw**
-  - Security was not a priority when TCP/IP was designed. The protocols do not inherently protect against common threats like spoofing, hijacking, or denial of service.
-  - IPv6 introduces some improvements, such as built-in IPsec, but these are optional and often not used, leaving the same vulnerabilities.
-
-- **Impact**
-  - Every modern application must implement its own security mechanisms (e.g., HTTPS, VPNs), leading to duplicated efforts and inconsistent protections.
-
----
-
-### 4. **Scalability Issues**
-
-- **IPv4 vs. IPv6**
-  - IPv4, with its 32-bit addressing, exhausted available addresses, leading to NAT (Network Address Translation) as a workaround. This introduced complexity and broke the end-to-end connectivity principle of the internet.
-  - IPv6, with 128-bit addressing, solves the address exhaustion problem but does not address underlying issues like routing table explosion or inefficiencies in the protocol stack.
-
-- **Routing Problems**
-  - The lack of built-in session and naming management makes routing inefficient. Large routing tables and decentralized updates slow down the internet and make it harder to scale.
-
----
-
-### 5. **No Support for Application-Centric Networking**
-- **TCP/IP’s Assumption**
-  - The protocol assumes communication happens between fixed endpoints (e.g., IP addresses). Modern applications, however, focus on data and services rather than specific endpoints. For example:
-    - Cloud applications may move across data centers.
-    - Mobile devices frequently change networks.
-  - TCP/IP’s static model is incompatible with this dynamic, service-oriented world.
-
-- **Impact**
-  - Workarounds like DNS (Domain Name System) and CDNs (Content Delivery Networks) add layers of complexity, but they’re still built on a flawed foundation.
-
----
-
-### RINA: A Better Alternative
-
-The **Recursive Inter-Network Architecture (RINA)** proposes a solution to the flaws of TCP/IP by rethinking the internet's architecture. Here’s how RINA addresses these issues[^1]:
-
-1. **Unified Layering**
-   - Unlike TCP/IP, which has rigid and distinct layers, RINA uses recursive layers. Each layer provides the same functionalities (e.g., routing, security, session management), simplifying the architecture.
-
-2. **Built-In Session Management**
-   - RINA natively supports session management, ensuring continuity and reliability for modern applications, even in the face of interruptions.
-
-3. **Application-Centric Networking:**
-   - RINA treats applications as first-class citizens, focusing on the services they need rather than rigid endpoint communication. This aligns with the dynamic nature of modern networks.
-
-4. **Improved Security:**
-   - Security is integral to RINA, with mechanisms for authentication, confidentiality, and integrity built into every layer.
-
-5. **Simplified Routing and Scaling:**
-   - RINA reduces the size and complexity of routing tables, making the network easier to scale and manage.
-
-[^1]: [RINA Leaflet](https://www.open-root.eu/IMG/pdf/rina-leaflet_20191115_en.pdf)

docs/main/first_principle_thinking/_category_.json

@@ -1,7 +0,0 @@
-{
-    "label": "First Principle Thinking",
-    "position": 4,
-    "link": {
-      "type": "generated-index"
-    }
-  }

docs/main/geoaware/_category_.json

@@ -1,7 +0,0 @@
-{
-    "label": "The solution",
-    "position": 3,
-    "link": {
-      "type": "generated-index"
-    }
-  }

docs/main/geoaware/geo_aware.md

@@ -1,32 +0,0 @@
----
-sidebar_position: 1
-title: 'What is Geo Awareness'
-hide_title: true
----
-
-![](img/geo_aware.png)
-
-## What is Geo Awareness
-
-**Geo-awareness** ensures that digital systems operate with respect to geographic and physical realities. This concept radically shifts how we approach storage, computation, and networking by enabling location-centric control and efficiency. Here's what it entails:
-
-#### Key Features of Geo-Awareness:
-
-1. **Shortest Physical Path for Communication**  
-   Communication between two parties happens through the shortest physical route, reducing latency and energy consumption while increasing efficiency.
-
-2. **Data Autonomy and Integrity**  
-   Users can decide where their data is stored. The data remains incorruptible and accessible only to the user or their personal AI agent, ensuring data privacy and autonomy.
-
-3. **Resilient Internet Functionality**  
-   Even in cases of internet outages or disasters, most apps and services remain operational, ensuring reliability and continuity.
-
-4. **Control Over Applications and AI**  
-   Geo-awareness enables users to decide where their applications and personal AI agents operate, giving them full control over their digital footprint and reducing external vulnerabilities.
-
-5. **Transparent Deployment of Code**  
-   Knowing exactly which code or app is deployed where ensures security and prevents tampering.
-
-6. **Relevance for Nations and Public Infrastructure**  
-   Unlike public blockchains that lack geo-awareness, this model empowers countries with localized control, enhancing autonomy and trust.
-

docs/main/geoaware/solution.md

@@ -1,64 +0,0 @@
----
-sidebar_position: 4
-title: 'Solution For a Better Internet'
-hide_title: true
----
-
-![](img/geo_aware2.png)
-
-## Geo Awareness is the Solution for Many of the Internet Problems
-
-### The Problems
-
-- [Compare Electricity](../internet_today/compare_electricity.md) - Compares the inefficiency of relying on distant internet infrastructure to the absurdity of using electricity generated on the other side of the world.
-- [Internet Basics](../internet_today/internet_basics.md) - Explains the three fundamental layers of the internet: compute/AI/storage, network, and applications, highlighting current centralization issues.
-- [Centralization Risk](../internet_today/centralization_risk.md) - Details the dangers of relying on centralized infrastructure and services, using real-world examples like the Ukraine conflict.
-- [The Race For Intelligence](../internet_reinvented/aci.md) - Discusses how AI agents will replace traditional apps within 2 years and the implications of centralized AI development.
-- [GDP Negative Impact](../internet_today/gdp_negative.md) - Reveals how the current internet structure causes economic losses for developing nations, with case studies showing billions in yearly losses.
-
-
-**The following table shows how the problems as listed above are fixed because of geo awareness.**
-
-
-| **Problem Area**                   | **Web2**                                                                                              | **Web3**                                                                             | **Web 4 = Geo-Aware**                                                                                 |
-| ---------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- |
-| **Centralization**                 | Dominated by a few corporations; creates fragility and dependency. | Often more Decentralized, but lacks local autonomy; often relies on centralized validators and still datacenters.     | Fully decentralized and location-specific, empowering local infrastructure and autonomy.   |
-| **Data Autonomy**               | Data stored in centralized data centers controlled by corporations.                                   | Decentralized storage, but users often lack control over physical location.          | Users choose specific locations for data storage, ensuring autonomy and privacy.           |
-| **Infrastructure Resilience**      | Vulnerable to disasters, geopolitical issues, and single points of failure.                           | Often less resilient compared to Web2.                      | Shortest physical paths and local redundancies ensure continued operation during disruptions. New paths are found when needed even by using nodes from your friends. |
-| **Economic Impact (GDP Negative)** | High costs for infrastructure; revenue flows to global platforms.                                     | The validators are still too centralized and often hosted in centralized datanceters. Too complicated and too early days to help right now. | Localized infrastructure boosts regional economies, keeping revenue within countries.         |
-| **Internet Efficiency**            | Long data routes; underutilized hardware; inefficient layers.                                         | Reliant on outdated protocols, vulnerable because of used ledger tech and layered inefficiencies. | Shortest paths reduce latency and cost; full hardware optimization ensures efficiency.        |
-| **Security and Transparency**      | Complex, security by smart employees of the corporations.                                             | Smart contracts improve security, but issues remain as code upgrade path.                            | Transparent and tamper-proof deployments ensure security and resilience.                      |
-| **Layer Complexity**               | Redundant layers create inefficiencies and fragility.                                                 | Often web3 is more complex compared to web 2.                     | Simplifies architecture by localizing compute, storage, and networking. 10x less development effort is possible                       |
-| **Application Hosting**            | Hosted in large centralized data centers, increasing latency and cost.                                | Sometimes, decentralized hosting but not geographically optimized.                              | Applications can be hosted locally, reducing latency and ensuring autonomy.                   |
-| **Access Inequality**              | Over 50% of the world lacks reliable access.                                                          | Expands access but without addressing local infrastructure challenges.               | Geo-aware systems build localized, affordable infrastructure to improve access.               |
-| **Session Management**             | Breaks under interruptions; no native continuity.                                                     | Some continuity improvements via decentralized protocols.                            | Built-in session management ensures reliability even during disruptions.                      |
-
-
-
-## Challenges in the Current Depin (Decentralized Internet) World
-
-Despite advancements in decentralized technology, geo-awareness remains under-prioritized. 
-
-Current Web3 solutions focus on decentralization without accounting for the geographic efficiency or autonomy that geo-awareness offers.
-
----
-
-## Comparison Table: Current Web3 Solutions vs. Geo-Aware Systems
-
-
-| **Feature**             | **Current Web3 Solutions**                              | **Geo-Awareness**                                        |
-| ----------------------- | ------------------------------------------------------- | -------------------------------------------------------- |
-| **Storage**             | Global, often randomly distributed without user control | Users choose storage locations; data remains autonomous   |
-| **Compute**             | Decentralized but lacks location-specific optimization  | Compute occurs at chosen locations; optimized for region |
-| **Network**             | Relies on global, non-optimized routing                 | Shortest physical path for communication                 |
-| **Ledger**              | Public blockchains are unreliable in case of network issues          | Location-aware autonomous ledgers for national and local control    |
-| **Resilience**          | Vulnerable to global internet disruptions               | Independent operation during outages                     |
-| **Application Control** | Limited transparency on app deployment locations and upgrade paths        | Full control and visibility of app deployment            |
-| **Data Integrity**      | Prone to distributed risks and complexities             | Tamper-proof, user-controlled data access                |
-
-
----
-
-## Why Geo-Awareness Matters
-
-The current centralized and globalized digital architecture exacerbates inefficiencies, compromises autonomy, and creates economic dependencies. Geo-awareness addresses these problems by creating a decentralized yet location-sensitive framework. This ensures that infrastructure is resilient, secure, and operates in harmony with the physical realities of the world, ultimately empowering users and nations alike.

docs/main/inca.md

@@ -1,100 +0,0 @@
----
-sidebar_position: 2
-title: 'ACI = The future is Now'
-hide_title: true
----
-
-
-![](https://threefold.info/tftech/assets/images/web0-4d67ef81ee465755e657ba4f7b1b9247.png)
-
-
-# The Future is Now
-## Augmented Collection Intelligence (ACI)
-
-Founded by Internet 1.0 Pioneers
-
-Welcome to the future of the internet, ACI, a logical evolution that rethinks and reinvents the foundations of how we connect, communicate, and collaborate globally.
-
-- The internet is burdened with inefficiencies, risks, and a growing dependency on centralization.
-- This legacy has left over 50% of the world without decent internet access, widened economic gaps, and exposed critical vulnerabilities.
-
-ThreeFold has created an alternative deployed today ready to scale to the planet.
-
-
-## +5 billion
-
-We are a **grounded** project:
-
-- Already deployed in +50 countries, +60,000 vcpu life.
-- 1 Country signed on for deployment, more coming. 
-- We didn't do any marketing yet, news will be released as we work on our Token Launch.
-
-## **The Future is here today**
-
-- AI Mind
-  - AI LLM's (large language model, prompts) Sovereign & geo aware, under control of ourselves and our community.  
-  - Be the provider of AI Mind (GPU Capacity) to your friends and yourself, and make a recurring income by doing so.
-  - Let's be smarter all together.
-  - **Cost to provision 1/10 compared to alternatives**
-- AI agents 
-  - The only Geo Aware agent techno in the world.
-  - Combination of humans & machines with the potential of the creation of Collective Augmented Intelligence
-  - 10x easier development of truly geo aware & decentralized app (super safe, flexible and scalable).
-  - **Cost to provision 1/10 compared to alternatives**
-- Compute/Storage
-  - The only Geo Aware Cloud (compute/storage) solution in the world.
-  - **Cost to provision 1/5 compared to alternatives**
-- The first 1 million cubits Quantum Computer in the world
-  - ThreeFold will deliver this capability end H1 2025 together with a parnter on top of the ThreeFold grid.
-  - **Cost to provision 1/10 compared to alternatives**
-
-> More info see [https://threefold.info/tftech](https://threefold.info/tftech)
-
-## SAFT = Safe Agreement for Future Tokens
-
-- Starting Feb 2025, we will raise 30-50m USD for the launch of our INCA token for ThreeFold.
-- This token will be launched on major platforms with the help of major partners & influencers.
-- The timing is right.
-
-Contact us for more info
-
-## Information about ThreeFold
-
-<div style={{
-  position: 'relative',
-  width: '100%',
-  height: 0,
-  paddingTop: '56.25%',
-  marginTop: '1.6em',
-  marginBottom: '0.9em',
-  overflow: 'hidden',
-  borderRadius: '8px',
-  willChange: 'transform'
-}}>
-  <iframe
-    src="https://www.canva.com/design/DAGZEbB_FN4/e98cXbAWyD1NGFQswDcePg/view?embed"
-    style={{
-      position: 'absolute',
-      width: '100%',
-      height: '100%',
-      top: 0,
-      left: 0,
-      border: 'none',
-      padding: 0,
-      margin: 0
-    }}
-    allowFullScreen={true}
-    allow="fullscreen">
-  </iframe>
-</div>
-
-<div style={{ marginTop: '10px' }}>
-  <a href="https://www.canva.com/design/DAGZEbB_FN4/e98cXbAWyD1NGFQswDcePg/view" 
-     target="_blank" 
-     rel="noopener"
-     style={{ textDecoration: 'none' }}>
-    Presentation ThreeFold Intro Jan 2025
-  </a>
-</div>
-
-

docs/main/internet_reinvented/_category_.json

@@ -1,7 +0,0 @@
-{
-    "label": "Internet Re-Invented",
-    "position": 3,
-    "link": {
-      "type": "generated-index",
-    }
-  }