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
Copy file name to clipboardexpand all lines: Concepts/Censorship.md
+3-6
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,3 @@
1
-
2
-
## Censorship
3
-
4
1
**Censorship** is the suppression or control of speech, communication, or information by a governing body or authority, often resulting in a lack of free expression and limited user autonomy.
5
2
6
3
Imagine you’ve been using a social platform to share your thoughts and connect with others. One day, you notice that your posts are disappearing or are no longer visible to your friends. Your reach is being reduced, and your voice is being silenced. This is an example of **censorship** at play—when someone else decides what you can and cannot say online, and what others can and cannot see.
@@ -17,7 +14,7 @@ However, this doesn't mean we should accept censorship without a solution. Inste
17
14
18
15
In **Pubky**, the approach is not to eliminate censorship entirely—because some level of censorship will always exist where there are centralized components—but rather to provide users with a way to **circumvent** it when it happens.
19
16
20
-
-**Flexible Hosting**: Pubky provides a flexible hosting model using trusted servers known as **Homeservers**. While these servers may be subject to censorship, Pubky ensures that users have the ability to migrate away from a censoring server whenever needed. Users can move their data, identities, and connections seamlessly, meaning they retain control even in the face of censorship.
17
+
-**Flexible Hosting**: Pubky provides a flexible hosting model using trusted servers known as [[Homeservers|homeservers]]. While these servers may be subject to censorship, Pubky ensures that users have the ability to migrate away from a censoring server whenever needed. Users can move their data, identities, and connections seamlessly, meaning they retain control even in the face of censorship.
21
18
22
19
-**Decentralized Identity**: In Pubky, user identities are not dependent on any single server. By using **self-issued public keys**, users maintain their identity even if they change hosting providers. This prevents identity loss when moving away from a server that engages in censorship.
23
20
@@ -26,13 +23,13 @@ In **Pubky**, the approach is not to eliminate censorship entirely—because som
26
23
## Important Aspects of Censorship Resistance
27
24
28
25
-**Data Control**: Users should always have access to and control over their data, even if one hosting provider chooses to censor it. Pubky’s approach empowers users by ensuring they are not dependent on any one server.
29
-
-**Migration and Interoperability**: The ability to migrate data, identities, and connections between different homeservers helps users remain resilient against censorship. Interoperable systems mean that even if one provider blocks content, another can provide access.
26
+
-**Migration and Interoperability**: The ability to migrate data, identities, and connections between different [[Homeservers|homeservers]] helps users remain resilient against censorship. Interoperable systems mean that even if one provider blocks content, another can provide access.
30
27
-**Local Copies and Self-Hosting**: Users can keep local copies of their data, and Pubky encourages self-hosting, giving users more control over what happens to their information and ensuring their content is not subjected to centralized oversight.
31
28
32
29
## Challenges and Considerations
33
30
34
31
-**Legal Compliance**: Censorship is often tied to legal requirements that hosting providers must comply with. Even decentralized systems will face challenges related to legal jurisdictions, and Pubky is designed to navigate but not entirely eliminate these legal issues.
35
32
-**Content Moderation**: Some forms of moderation are necessary—whether it's to filter out spam or harmful content. Pubky facilitates **user-controlled moderation**, where individuals or groups decide what they want to see, rather than a centralized authority imposing a one-size-fits-all policy.
36
-
-**Redundancy Limitations**: While Pubky's redundancy and migration features provide resilience, they depend on the presence of multiple homeserver options. During the early phases, users may face limited availability of alternative servers.
33
+
-**Redundancy Limitations**: While Pubky's redundancy and migration features provide resilience, they depend on the presence of multiple [[Homeservers|homeservers]] options. During the early phases, users may face limited availability of alternative servers.
37
34
38
35
Censorship on the web is inevitable, but that doesn't mean users have to be powerless. With Pubky, you have the ability to choose your hosting, migrate your data, and maintain your identity—all key tools for resisting censorship. Pubky's design assumes censorship will happen and provides the mechanisms needed to overcome it. This empowers users with true control, ensuring that no single entity can unilaterally suppress their voice. The future of the web lies in resilient, user-first systems that put individuals back in control of their online presence.
Copy file name to clipboardexpand all lines: Concepts/Credible Exit.md
+2-5
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,3 @@
1
-
2
-
## Credible Exit
3
-
4
1
**Credible Exit** is the ability to leave a platform or service without losing access to your data, identity, or connections, ensuring full user control and portability.
5
2
6
3
This [substack post](https://subconscious.substack.com/p/credible-exit) by Gordon Brander is a good introduction to the topic.
@@ -15,7 +12,7 @@ Today, most platforms hold your data hostage. They make it difficult to leave, a
15
12
16
13
Here are some of the best examples of Credible Exit in practice:
17
14
18
-
-**Domain Name System (DNS)**: DNS is a classic example of a system that allows for a credible exit. If you no longer want your domain hosted with one provider, you can transfer it to another without losing control over your domain name.
15
+
-**Domain Name System (DNS)**: [[DNS]] is a classic example of a system that allows for a credible exit. If you no longer want your domain hosted with one provider, you can transfer it to another without losing control over your domain name.
19
16
-**Email Protocols (IMAP/SMTP)**: Email is another example. Users can change email providers while keeping the same email address, ensuring they don't lose their communication history or contacts.
20
17
-**Bitcoin Wallets**: Bitcoin wallets offer credible exit by allowing users to export private keys and import them into another wallet provider, retaining full control over their funds and transactions.
21
18
@@ -31,7 +28,7 @@ In **Pubky**, Credible Exit is not just an idea—it's built into the architectu
31
28
32
29
-**Data Portability**: Pubky’s design ensures that all of your data can be easily exported and imported between servers. This keeps your content intact and visible, regardless of where it’s hosted.
33
30
34
-
(NOTE: During Pubky's initial bootstrapping phase, credible exit may not be practically possible until more homeserver providers join. Synonym is building tools to make it easy for businesses and users to self-host.)
31
+
> _NOTE_: During Pubky's initial bootstrapping phase, credible exit may not be practically possible until more homeserver providers join. [Synonym](https://synonym.to/) is building tools to make it easy for businesses and users to self-host.
Copy file name to clipboardexpand all lines: Concepts/Semantic Social Graph.md
+2-43
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,3 @@
1
-
## Semantic Social Graph
2
-
3
1
A **Semantic Social Graph** represents relationships between users, content, and interactions, enriched with contextual meaning that enables better filtering, discovery, and coordination.
4
2
5
3
Imagine being able to not only see what your friends are sharing but also easily find content that matches your interests across a wide network of people you trust.
@@ -24,54 +22,15 @@ In **Pubky**, a decentralized Semantic Social Graph is central to providing a mo
24
22
25
23
This diagram shows how a Semantic Social Graph works, representing users, content, and tags. Users tag content and peers, which adds context and helps determine how information flows through the network. Relationships are weighted (Pubky weighting features are under development), meaning users can specify trust levels and the strength of connections to further personalize their experience.
26
24
27
-
```mermaid
28
-
graph LR
29
-
subgraph Users
30
-
U1[User A]
31
-
U2[User B]
32
-
U3[User C]
33
-
end
34
-
35
-
subgraph Data
36
-
C1[Post 1]
37
-
C2[Post 2]
38
-
C3[File 1]
39
-
end
40
-
41
-
subgraph Tags
42
-
T1[Tag: Blockchain]
43
-
T2[Tag: Decentralization]
44
-
T3[Tag: Privacy]
45
-
end
46
-
47
-
%% Users tag content
48
-
U1 --|tags with T1|--> C1
49
-
U1 --|tags with T2|--> C2
50
-
U2 --|tags with T2|--> C3
51
-
U3 --|tags with T3|--> C1
52
-
53
-
%% Users tag peers
54
-
U1 --|tags with T2|--> U2
55
-
U2 --|tags with T1|--> U3
56
-
57
-
%% Content linked to tags
58
-
C1 --|associated with|--> T1
59
-
C1 --|associated with|--> T3
60
-
C2 --|associated with|--> T2
61
-
C3 --|associated with|--> T2
62
-
63
-
%% Weighted relationships (represented by edge labels)
64
-
U1 --|strong connection|--> U2
65
-
U1 --|moderate connection|--> U3
66
-
```
25
+
67
26
68
27
**Tags and Contextual Meaning**: Pubky allows users to add tags to content and connections, giving them the ability to add context to their relationships. This means users can easily categorize and prioritize content based on what matters to them most.
69
28
70
29
-**Web of Trust**: The concept of **Web of Trust** is foundational to the Semantic Social Graph. Users can assign contextual trust to their connections, allowing for a more nuanced approach to content discovery and filtering. Instead of seeing content from strangers or questionable sources, users can prioritize info from people they trust.
71
30
72
31
-**Decentralized Indexing**: Pubky provides a decentralized approach to indexing, meaning that users aren't reliant on a single entity to determine the importance or visibility of content. Users have the power to decide what they want to see and how they want their views into the social graph to evolve.
73
32
74
-
(NOTE: During the initial bootstrapping phase of Pubky, the Semantic Social Graph may be limited in decentralization until more builders adopt the system. Synonym is actively developing tools to make it easier to run a Pubky homeserver, or self-host.)
33
+
> _NOTE_: During the initial bootstrapping phase of Pubky, the Semantic Social Graph may be limited in decentralization until more builders adopt the system. Synonym is actively developing tools to make it easier to run a Pubky [[Homeservers|homeserver]], or self-host.
4
3
5
4
**Semantic Relationships:** Connections between users and content are tagged with meaningful metadata, capturing the context, relevance, and nature of each relationship.
6
5
**Weighted Connections:** Relationships aren't just binary; they carry weights that represent their strength, trust level, or relevance, enabling more sophisticated interactions.
Copy file name to clipboardexpand all lines: Pubky App/App Architectures/1. Introduction.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
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.
1
+
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 [[Homeservers|homeservers]], through standardized read and write operations.
2
2
3
3
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.
4
4
5
-
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:
5
+
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|homeservers]] to more complex applications with custom aggregators and backends capable of powerful inference:
0 commit comments