init

collections/tech/.done

@@ -0,0 +1 @@
+3node_simple.png

collections/tech/architecture/architecture.md

@@ -3,5 +3,21 @@
 
 ![](img/architecture.png)
 
+### TF Nodes (or 3Nodes)
+
+The network of nodes which make up the cloud, each node provides compute, storage and network capacity.
+
+### TF Routers
+
+With the introduction of new devices in TFGrid 4.0, anyone can now operate as a network service provider.
+
+TF Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
+
+These TF Routers are not only compatible with Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
+
+### Web3 & Decentralized AI Compatibility
+
+The TFGrid is the ideal platform for hosting any Web3 and AI workloads. Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
 
 
+> Any workload (web2/3 and AI) can run on TFGrid.

collections/tech/architecture/img/.done

@@ -0,0 +1 @@
+architecture.png

collections/tech/history/c64.md

@@ -1,9 +1,13 @@
 ## we forgot to use hardware well
 
-The IT world does not utilize computer hardware well.
+The IT world fails to harness the full potential of computer hardware.
 
-![](img/c64.png)
+![Commodore 64](img/c64.png)
 
-Hardware advancements surged, while experiences and features stagnated, unable to match the pace. 
+While hardware advancements have surged forward, user experiences and features have often stagnated, failing to keep pace with these developments.
 
-> TODO: c64 describe better
+The original Commodore 64, with only 64 KB of memory, was a remarkably capable machine for its time. In contrast, today's computers boast 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.
+
+At Threefold, we are committed to bridging this gap by optimizing our approach to hardware utilization, thereby unlocking its full potential.

collections/tech/history/layers.md

@@ -8,4 +8,31 @@ This is due to a number of reasons.
 
 ![](img/fourreasons.png)
 
->TODO: 
+
+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.
+
+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.
+
+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 blocks 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.

collections/tech/innovations/img/.done

@@ -0,0 +1 @@
+qsss.png

collections/tech/internet/.done

@@ -0,0 +1,3 @@
+global_net.png
+network_path.png
+we_are_products.png

collections/tech/natural_progression/.done

@@ -0,0 +1 @@
+arch_minimal.png

collections/tech/nature/.done

@@ -0,0 +1 @@
+scaleout.png

collections/tech/nature/nature.md

@@ -0,0 +1,19 @@
+
+# ThreeFold grid inspired by nature
+
+![](nature.png)
+
+- Just like we have trillions of cells in our body, so can billions of twins live next to each other
+- Each twin has memory, knows how to communicate, has knowledge, history, ...
+- Twins like cells cannot live without a body = TFGrid.
+
+## This approach scales for ever
+
+![](scaleout.png)
+
+- There can be unlimited amounts 3Nodes and 3Bots (Digital Twins)
+- There are no bottlenecks nor centralization points
+- Our peer2peer network technology takes care of routing and security issues between the Twins and the TFNodes (3Nodes). The shortest paths is always looked for.
+
+
+

collections/tech/primitives/compute/compute.md

@@ -3,6 +3,22 @@
 
 ![](img/tfgrid_compute_.jpg)
 
-We are more than just Container or VM technology, see [our Beyond Container Document](../../primitives/compute/beyond_containers.md).
+We are more than just Container or VM technology.
 
-For more information see [ZeroOS](../../zos/zos_toc.md)
+Default features:
+
+- compatible with Docker
+- compatible with any VM (Virtual Machine)
+- compatible with any Linux workload
+- integrated unique storage & network primitives
+
+We have following unique advantages:
+
+- no need to work with images, we work with our unique ZOS FS
+- every container runs in a dedicated virtual machine providing more security
+- the containers talk to each other over a private network (mycelium)
+- the containers can use a web gatewat to allow users on the internet connect to the applications as running in their secure containers 
+- can use core-x to manage the workload
+
+
+For more information see [ZeroOS](zos.md)

collections/tech/primitives/compute/zmachine.md

@@ -1,5 +1,6 @@
 # ZMachine
 
+![](img/zmachine_zos_.jpg)
 
 
 ### Features
@@ -11,12 +12,5 @@
 *   minimal hacking surface to the Zero-Nodes, integrate silicon route of trust
 *   ZOS Filesystem: dedupe, zero-install, hacker-proof
 *   Webgateway: intelligent connection between web (internet) and container services
-*   integration with ZNet (efficient, secure encrypted network between the zmachines)
-*   Planetary Net: a true global single backplane network connecting us all
-
-### Architecture
-
-![](img/zmachine_zos_.jpg)
-
-A ZMachine is running as a virtual machine on top of Zero-OS.
+*   integration with Mycelium (efficient, secure encrypted network between the zmachines)
 

collections/tech/primitives/network/.done

@@ -0,0 +1 @@
+net1.png

collections/tech/qsss/.done

@@ -0,0 +1 @@
+qsss_overview.png

collections/tech/smartcontract_it/smartcontract_it_intro.md

@@ -1,4 +1,4 @@
-## Smart Contract for IT Intro
+## Smart Contract for IT 
 
 Ability for developers to launch IT workloads (applications) on the ThreeFold Grid using our TFGrid primitives secured by blockchain concepts.
 

collections/tech/technology_infrastructure.md

@@ -15,7 +15,6 @@ ThreeFold nodes provide Internet (storage, compute and network) to the people ar
 There are multiple ways how people can interactive without our platform (as developer or IT expert = sysadmin):
 
 ![](img/architecture_usage.png)  
-![alt text](image.png)
 
 
 

collections/tech/zos/flist_hub.md

@@ -6,7 +6,5 @@ You can convert an existing docker image the same way.
 
 Public hub: [hub.grid.tf](https://hub.grid.tf)
 
-If you want to experiment the hub and features, you could use the [playground hub](https://playground.hub.grid.tf).
-This hub could be reset anytime, don't put sensitive or production code there.