You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each service has its own copy. Each has different terms. Each can change the rules, lock you out, or shut down. You're a tenant in someone else's building.
|**You choose where data lives**| Your server, trusted provider, local device |
74
+
|**Apps come to your data**| Instead of giving data to apps |
75
+
|**You control access**| Grant, revoke, audit permissions |
76
+
|**You can leave**| Export everything, switch providers |
77
+
|**Data is interoperable**| Same data works across apps |
78
+
79
+
## Why It Matters
80
+
81
+
### Privacy
26
82
27
-
1.**You choose where your data lives** — Your server, a trusted provider, or anywhere you want
28
-
2.**Apps come to your data** — Instead of giving your data to apps, apps request access
29
-
3.**You control access** — Grant, revoke, and audit who can see what
30
-
4.**You can leave** — Export everything, switch providers, no lock-in
83
+
Your data isn't harvested to:
84
+
- Train AI models you don't consent to
85
+
- Build advertising profiles
86
+
- Be sold to data brokers
87
+
- Be leaked in breaches you didn't cause
88
+
89
+
### Control
90
+
91
+
You decide:
92
+
- Who sees what
93
+
- How long they have access
94
+
- What they can do with it
95
+
- When to revoke access
96
+
97
+
### Portability
98
+
99
+
No lock-in:
100
+
- Switch photo apps without losing photos
101
+
- Change social networks without losing connections
102
+
- Move providers without starting over
103
+
104
+
### Longevity
105
+
106
+
Your data survives:
107
+
- Services shutting down
108
+
- Companies being acquired
109
+
- Policy changes
110
+
- Account suspensions
31
111
32
112
## How SAND Implements This
33
113
34
114
### Solid Pods
35
115
36
-
[Solid](/protocols/solid) provides the primary mechanism for data sovereignty. A Solid pod is like a personal web server where all your data lives:
116
+
[Solid](/protocols/solid) provides the primary mechanism for data sovereignty. A Solid pod is a personal web server where your data lives:
37
117
38
118
```
39
119
your-pod.example.com/
40
120
├── profile/
41
-
│ └── card # Your identity
121
+
│ └── card # Your identity (WebID)
42
122
├── photos/
43
123
│ ├── 2024/
44
124
│ └── 2023/
45
125
├── documents/
46
126
│ └── notes/
127
+
├── social/
128
+
│ ├── contacts
129
+
│ └── messages
47
130
└── settings/
131
+
└── prefs.ttl
48
132
```
49
133
50
134
Apps don't store your data — they read from and write to your pod with your permission.
51
135
52
136
### Nostr Events
53
137
54
-
[Nostr](/protocols/nostr) stores messages and events cryptographically signed with your key. Even though events are distributed across relays, they're provably yours because only you have the private key.
138
+
[Nostr](/protocols/nostr) stores messages and events cryptographically signed with your key. Even though events are distributed across relays:
139
+
140
+
- They're provably yours (only you have the private key)
141
+
- Multiple relays provide redundancy
142
+
- No single point of failure
143
+
- You can move between clients freely
55
144
56
145
### DIDs
57
146
58
-
[Decentralized Identifiers](/protocols/did) ensure your identity isn't tied to any provider. Your DID works everywhere, and you control the keys.
147
+
[Decentralized Identifiers](/protocols/did) ensure your identity isn't tied to any provider:
148
+
149
+
- Your DID works everywhere
150
+
- You control the keys
151
+
- No platform can take your identity
152
+
- Portable across the entire web
153
+
154
+
## Comparison
155
+
156
+
| Aspect | Centralized | Sovereign |
157
+
|--------|-------------|-----------|
158
+
|**Data location**| Service's servers | Your choice |
159
+
|**Terms of service**| Their rules | Your rules |
160
+
|**Service shutdown**| Data lost | Data persists |
161
+
|**App switching**| Start over | Data stays |
162
+
|**AI training**| Your data used | You decide |
163
+
|**Privacy**| Trust them | Trust yourself |
164
+
|**Portability**| Maybe export | Full ownership |
165
+
166
+
## Real-World Examples
167
+
168
+
### Photos
169
+
170
+
**Today:** Upload to Instagram → Instagram owns the relationship with your data, can delete, ban, change terms.
171
+
172
+
**Sovereign:** Store in your pod → Use any photo app that can read from your pod. Switch apps without losing photos. Your AI can organize them.
173
+
174
+
### Documents
175
+
176
+
**Today:** Write in Google Docs → Google can read everything, train AI on your content, change pricing.
177
+
178
+
**Sovereign:** Write to your pod → Use any editor. Documents survive any single service. Full export always available.
179
+
180
+
### Social Graph
181
+
182
+
**Today:** Build network on LinkedIn → LinkedIn owns your connections. Leave = lose everything.
183
+
184
+
**Sovereign:** Contacts in your pod → Take your network anywhere. Any social app can read (with permission).
185
+
186
+
## Challenges
187
+
188
+
### Convenience
189
+
190
+
Sovereign systems require more setup than signing up for a free service. This is improving:
191
+
- Hosted pod providers
192
+
- Better tooling
193
+
- Simpler apps
194
+
195
+
### Network Effects
196
+
197
+
Value often comes from others using the same platform. Federation and bridges help:
198
+
- Nostr clients are interoperable
199
+
- ActivityPub connects Fediverse
200
+
- Bridges connect protocols
59
201
60
-
##Practical Benefits
202
+
### Technical Complexity
61
203
62
-
| Centralized | Sovereign |
63
-
|-------------|-----------|
64
-
| Service shuts down, data gone | Your data persists |
65
-
| Terms change, you comply or leave | You set the terms |
66
-
| Data siloed per app | One dataset, many apps |
67
-
| Export is limited | Full data portability |
68
-
| Vendor lock-in | Switch providers freely |
204
+
Running your own infrastructure requires knowledge. Solutions:
205
+
- Managed providers
206
+
- One-click deployments
207
+
- Local-first apps
69
208
70
209
## Getting Started
71
210
72
211
1.**Set up a pod** — Use [Sandymount](/projects/sandymount) to run your own, or choose a provider
73
-
2.**Use pod-aware apps** — Applications that work with Solid pods
74
-
3.**Control access** — Learn how to manage permissions
212
+
2.**Create a Nostr identity** — Generate keys with [Noskey](/projects/noskey) or any client
213
+
3.**Use sovereign apps** — Applications that work with your data
214
+
4.**Control access** — Learn to manage permissions
75
215
76
216
See [Your First Pod](/guides/your-first-pod) for a hands-on tutorial.
77
217
78
218
## Learn More
79
219
80
220
-[Solid Protocol](/protocols/solid) — The technical specification
**Git over Nostr.** Send and receive patches via the protocol.
9
+
10
+
## Overview
11
+
12
+
GitStr enables distributed version control by sending and receiving Git patches over Nostr, implementing NIP-34. Censorship-resistant code collaboration.
0 commit comments