mirror of
https://github.com/aljazceru/pubky-knowledge-base.git
synced 2025-12-18 14:24:22 +01:00
fix: capitalization
This commit is contained in:
33
.obsidian/workspace.json
vendored
33
.obsidian/workspace.json
vendored
@@ -164,29 +164,30 @@
|
||||
"quartz/public/quartz/quartz/static/icon.png",
|
||||
"quartz/public/static/og-image.png",
|
||||
"quartz/public/static/icon.png",
|
||||
"concepts/Web of Trust.md",
|
||||
"pubky-app.md",
|
||||
"index.md",
|
||||
"Pubky App.md",
|
||||
"TLDR.md",
|
||||
"Concepts/Web of Trust.md",
|
||||
"pubky.app.md",
|
||||
"Pubky.app.md",
|
||||
"concepts/Credible Exit.md",
|
||||
"concepts/Censorship.md",
|
||||
"Concepts/Credible Exit.md",
|
||||
"Concepts/Censorship.md",
|
||||
"pkarr/Why Pkarr.md",
|
||||
"pubky-core/Protocols.md",
|
||||
"pubky-core/Data Stores.md",
|
||||
"technologies/Paykit.md",
|
||||
"Pubky Core/Protocols.md",
|
||||
"Pubky Core/Data Stores.md",
|
||||
"Technologies/Paykit.md",
|
||||
"pubky-core/Data.md",
|
||||
"data store.md",
|
||||
"technologies/Mainline DHT.md",
|
||||
"pubky-core/Applications.md",
|
||||
"pubky-core/pubky-core.md",
|
||||
"index.md",
|
||||
"technologies/HTTPS.md",
|
||||
"technologies/DoH.md",
|
||||
"technologies/DNS.md",
|
||||
"technologies/DHT.md",
|
||||
"Technologies/Mainline DHT.md",
|
||||
"Pubky Core/Applications.md",
|
||||
"Pubky Core/pubky-core.md",
|
||||
"Technologies/HTTPS.md",
|
||||
"Technologies/DoH.md",
|
||||
"Technologies/DNS.md",
|
||||
"Technologies/DHT.md",
|
||||
"related-tech/Mainline DHT.md",
|
||||
"related-tech/DHT.md",
|
||||
"related-tech/DNS.md",
|
||||
"pkarr/Why Pkarr?.md"
|
||||
"Pkarr/Why Pkarr?.md"
|
||||
]
|
||||
}
|
||||
4
ELI5.md
4
ELI5.md
@@ -1,7 +1,7 @@
|
||||
## ELI5: Pubky Explained for Children
|
||||
|
||||
Like a kite, [data](pubky-core/Data%20Stores.md) is in the cloud, but you hold its string.
|
||||
Like a kite, [data](Data%20Stores.md) is in the cloud, but you hold its string.
|
||||
|
||||
Your friends can find your messages by finding your kite in the sky ([[Pkarr]] in the [[DHT]]) and following the string down to the message board you are currently posting on.
|
||||
|
||||
You can move your kite (your [data](pubky-core/Data%20Stores.md)) anywhere and your friends will still be able to find it as long as you are holding the string of the kite ([[Pkarr]] private key).
|
||||
You can move your kite (your [data](Data%20Stores.md)) anywhere and your friends will still be able to find it as long as you are holding the string of the kite ([[Pkarr]] private key).
|
||||
|
||||
@@ -21,7 +21,7 @@ The core idea is to streamline the process of publishing and resolving resource
|
||||
|
||||
## Getting Started
|
||||
|
||||
[To start using Pkarr](/pkarr/Getting%20Started%20with%20Pkarr.md), you can visit the [web app demo](https://app.pkarr.org) or explore the Rust examples provided in [Pkarr repository](https://github.com/Nuhvi/pkarr/).
|
||||
[To start using Pkarr](Getting%20Started%20with%20Pkarr.md), you can visit the [web app demo](https://app.pkarr.org) or explore the Rust examples provided in [Pkarr repository](https://github.com/Nuhvi/pkarr/).
|
||||
|
||||
### Publishing Resource Records
|
||||
|
||||
@@ -12,8 +12,8 @@ Pubky-app's initial focus is building a decentralized social media protocol. Key
|
||||
|
||||
- [[Search]]ing profiles and posts
|
||||
|
||||
- Notification delivery through [Application](pubky-core/Applications) Backends
|
||||
- Notification delivery through [Application](Applications.md) Backends
|
||||
|
||||
- Distributed moderation through [user blocking](concepts/Web%20of%20Trust.md)
|
||||
- Distributed moderation through [user blocking](Web%20of%20Trust.md)
|
||||
|
||||
The goal is to recreate core social features without dependence on any centralized company or platform.
|
||||
@@ -10,7 +10,7 @@ Application Backends power features by integrating aggregated data:
|
||||
|
||||
- Communities facilitate moderation and discovery around shared interests.
|
||||
|
||||
- [Payments](/technologies/Paykit.md) handle microtransactions like tipping within a peer-to-peer economy.
|
||||
- [Payments](Paykit.md) handle microtransactions like tipping within a peer-to-peer economy.
|
||||
|
||||
- Identity services provide single sign-on through self-sovereign credentials.
|
||||
|
||||
@@ -10,7 +10,7 @@ Pubky is built on a few core concepts:
|
||||
|
||||
- **[[Search]]** - Services that index aggregated data and enable full text/attribute searches.
|
||||
|
||||
- **[Application Backends](/pubky-core/Applications.md)** - Backend services that integrate feeds, search, and user interfaces/configurations.
|
||||
- **[Application Backends](Applications.md)** - Backend services that integrate feeds, search, and user interfaces/configurations.
|
||||
|
||||
- **[[Pkarr]]** - Self-issued public keys that function as sovereign, publicly addressable domains are used to resolve the previous components.
|
||||
|
||||
10
TLDR.md
10
TLDR.md
@@ -1,10 +1,10 @@
|
||||
## TLDR; [pubky.app](pubky-app) in Brief
|
||||
## TLDR; [pubky.app](Pubky%20App.md) in Brief
|
||||
|
||||
[pubky.app](pubky-app) is a decentralized alternative to social media platforms like Twitter. It uses a distributed architecture where:
|
||||
[pubky.app](Pubky%20App.md) is a decentralized alternative to social media platforms like Twitter. It uses a distributed architecture where:
|
||||
|
||||
- Users host their own data on independent [[data stores]]
|
||||
- Services [aggregate](pubky-core/Aggregators.md) data across stores into a unified view
|
||||
- Users host their own data on independent [[Data Stores]]
|
||||
- Services [aggregate](Aggregators.md) data across stores into a unified view
|
||||
- [[Feeds]] and search present curated views of the aggregated data
|
||||
- [Application](pubky-core/Applications.md) back-ends integrate features without centralized control
|
||||
- [Application](Applications.md) back-ends integrate features without centralized control
|
||||
|
||||
The end goal is to give individuals self-sovereign digital identity and true ownership over social profiles/activity without fear of data misuse or account bans by any single entity.
|
||||
|
||||
1
Technologies/Paykit.md
Normal file
1
Technologies/Paykit.md
Normal file
@@ -0,0 +1 @@
|
||||
Paykit abstracts and automates any payment method behind a single, static public key. The public key belongs to a Pubky instance and points to a [data store](Data%20Stores.md) containing all supported payment endpoints. Paykit enables applications where users pay directly to profiles, so offers a very intuitive experience, particularly when multiple payment methods are possible within the system.
|
||||
6
index.md
6
index.md
@@ -2,12 +2,12 @@
|
||||
title: Welcome to the Pubky Knowledge Base
|
||||
---
|
||||
|
||||
This is the [[pubky-core]] and [pubky.app](pubky-app) knowledge base. Currently these docs are a mix of reality, dreams, visions, technicalities, actuality and plans.
|
||||
This is the [[pubky-core]] and [pubky.app](Pubky%20App.md) knowledge base. Currently these docs are a mix of reality, dreams, visions, technicalities, actuality and plans.
|
||||
|
||||
1. Cloud storage with [[Credible Exit]] (in the current implementation it is just a web server + [[Pkarr]].org)
|
||||
2. On top of that we build a [[Web of Trust]]
|
||||
3. [pubky.app](pubky-app) is the main demonstration of how should this distributed data be crawled, indexed and searched at scale (albeit at a centralized setup).
|
||||
3. [pubky.app](Pubky%20App.md) is the main demonstration of how should this distributed data be crawled, indexed and searched at scale (albeit at a centralized setup).
|
||||
|
||||
## Get Started
|
||||
|
||||
A good place to start is the [pubky.app](pubky-app) [[TLDR]] or our pubky-core [[ELI5]]
|
||||
A good place to start is the [pubky.app](Pubky%20App.md) [[TLDR]] or our pubky-core [[ELI5]]
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
Paykit abstracts and automates any payment method behind a single, static public key. The public key belongs to a Pubky instance and points to a [data store](pubky-core/Data%20Stores.md) containing all supported payment endpoints. Paykit enables applications where users pay directly to profiles, so offers a very intuitive experience, particularly when multiple payment methods are possible within the system.
|
||||
Reference in New Issue
Block a user