Implementation of Knowledge Organization Infrastructure Network (KOI-net) protocol in Python
KOI-net Protocol Specification Draft v1.0
The KOI-net protocol defines the standard communication patterns and coordination norms needed to establish and maintain Knowledge Organization Infrastructure (KOI) networks. KOI networks are heterogeneous compositions of KOI nodes, each of which is capable of autonomously inputting, processing, and outputting knowledge. The behavior of each node and configuration of each network can vary greatly; therefore, the protocol is designed to be a simple, flexible, and interoperable foundation for future projects to build on. The protocol only governs communication between nodes, not how they operate internally. As a result we consider KOI-nets to be fractal-like, in that a network of nodes may act like a single node when viewed from outside.
sensemaker.computer/sensemaker-cli
Sensemaker's CLI for protocol-native interaction on ATProto.
Blog | Lexicon Community | Offprint
A working group that stewards a shared namespace for AT Protocol schemas: built in the open, governed collectively, and free for anyone to use.
Knowledge Networks and the Politics of Protocols
Harmony without loss of Variety; Variety without loss of Harmony.
A conceptual model of ATProto and ActivityPub
If you were to design an open social networking protocol, what would that look like? Which metaphors and comparisons would you use to get a general idea of how the network functions? And what would you answer if people ask if your network is decentralised and federated?
The Story of Python and how it took over the world | Python: The Documentary
From ZK-first to AT Protocol — our path to DDS | Agora Citizen Network
We've been building Agora — a platform for public deliberation using Polis-style clustering — for a while now. Along the way, we've written about what we think about Nostr, AT Protocol, Polis, Community Notes, and protocol interoperability. Those posts are somewhat outdated now. This one describes w...
third-party apis: community infrastructure on atproto - Keith's Thoughts
you can just build things from an open set of tools
Introducing any-llm: A unified API to access any LLM provider
When it comes to using LLMs, it’s not always a question of which model to use: it’s also a matter of choosing who provides the LLM and where it is deployed. Today, we announce the release of any-llm, a Python library that provides a simple unified interface to access the most popular providers.
Longer version: Eurosky’s plc.eurosky.network is a small but real ATProto infrastructure move. It is not “a European Bluesky clone.” It is a read replica of the did:plc identity directory — the layer many accounts use to resolve keys, handles, and PDS hosts.
Knowledgebase Apps
Long form writing. Group access control. OIDC so we can use atproto. The commercial versions would be Notion or Confluence. An open version would be Outline Wiki.
Fichiers - La Suite Numérique
Docs - La Suite Numérique
Docs — Turn your team's content into knowledge
Enterprise-ready Wiki for Teams | Docmost
Outline – Team knowledge base & wiki
self-hostable notion replacements (by Tyler Lawson) — Semble
