From 9b03021d574fc678f583f5862c6edd874abbcdce Mon Sep 17 00:00:00 2001
From: John Carvalho <18273620+BitcoinErrorLog@users.noreply.github.com>
Date: Wed, 9 Oct 2024 09:45:00 +0100
Subject: [PATCH] Delete App Architectures/1. Introduction.md

---
 App Architectures/1. Introduction.md | 9 ---------
 1 file changed, 9 deletions(-)
 delete mode 100644 App Architectures/1. Introduction.md

diff --git a/App Architectures/1. Introduction.md b/App Architectures/1. Introduction.md
deleted file mode 100644
index cfb194b..0000000
--- a/App Architectures/1. Introduction.md	
+++ /dev/null
@@ -1,9 +0,0 @@
-Leveraging the [[Pubky Core/Introduction|Pubky Core]] protocol as the foundational layer, we can envision a diverse array of applications with distinct functionalities. While each app can implement its own unique design patterns and user interfaces, they all share a common underlying architecture: interacting with the distributed data stores, colloquially referred to as [[Data Stores |home servers]], through standardized read and write operations.
-
-The [[Pubky Core/Introduction|Pubky Core protocol]] enables a decentralized approach to data management, facilitating seamless communication between clients and their respective data stores. This architecture promotes data sovereignty and enhances system resilience.
-
-Below, we present several high-level designs that showcase the versatility of this architecture, from simple client (browser) apps that interact directly with one or several homeservers to more complex applications with custom aggregators and backends capable of powerful inference:
-
-- [[2. Client - Homeserver|Client-Homeserver]]
-- [[4. Custom Backend|Custom backend]]
-- [[3. Global Aggregators|Global aggregators]]