Multi-dimensional key-value documents with an efficient synchronization protocol.
y-atproto - npmx
A [Yjs](https://yjs.dev/) CRDT provider that syncs documents over the [AT Protocol](https://atproto.com/). Documents are stored as ATProto records and real-time updates are delivered via [Jetstream](https://github.com/bluesky-social/jetstream).
haierkeys/fast-note-sync-service
High-performance, low-latency note synchronization, online management, and remote REST API service platform.
Fast Note Sync
Real-time sync of your vaults across server, mobile, and web; shareable with anyone; supports REST and MCP integrations to build your personal AI knowledge base.
Open Exchange Architecture
A specification for representing scientific documents and their components as structured objects.
Open Exchange Architecture
A specification for representing scientific documents and their components as structured objects.
Open Exchange Architecture
A specification for representing scientific documents and their components as structured objects.
Scientific Documents as First-Class Objects on AT Protocol
OXA now defines an AT Protocol lexicon for publishing scientific documents to the Atmosphere. The `pub.oxa.*` namespace lets documents live in any Personal Data Server, making scientific content user-owned, portable, and discoverable alongside social interactions, feeds, and moderation infrastructure.
Scientific Documents as First-Class Objects on AT Protocol
OXA now defines an AT Protocol lexicon for publishing scientific documents to the Atmosphere. The `pub.oxa.*` namespace lets documents live in any Personal Data Server, making scientific content user-owned, portable, and discoverable alongside social interactions, feeds, and moderation infrastructure.
Your decentralised & privacy enhancing alternative to google docs
Decentralised Docs: peer-to-peer document editor that keeps your data secure with end-to-end encryption. Real-time collaboration, onchain.
STAR: ordered key-value archive format #21
Hello! I'd like to propose new work for DASL: the [STAR](https://tangled.org/microcosm.blue/star/tree/main/v1-star) (/STAR-lite) archive format. I originally made STAR as a stricter, simpler, safer, more efficient alternative to CARs for atproto public repository exports. Its v0 now has several library implementations and has at least two production producers and half a dozen consumers in the Atmosphere, but is very atproto-coupled. STAR is [being considered](https://github.com/bluesky-social/proposals/pull/114) as the standard format for [atproto spaces](https://github.com/bluesky-social/proposals/tree/main/0016-permissioned-data) repo exports. After iteration with @dholms.at and @bnewbold.net, STAR's spaces-compatible v1 is becoming a more general-purpose format for ordered key-value data, and I think, a potentially good fit with DASL. Following the DASL governance [steps for proposing new work](https://dasl.ing/governance.html#:~:text=Proposing%20New%20Work): ## What will be implemented A specification ([in progress](https://tangled.org/microcosm.blue/star/tree/main/v1-star)), reference implementations, test vectors. ## Who wants it Data exports in atproto is one established use-case. People have been motivated to request public archives in STAR-lite format from [hubble](https://web.hubble.microcosm.blue/): 260M STAR-lite archives served vs 6M CAR. Repositories compress to a bit under half the size compared to CARs, which translates directly into faster network backfill rate in many cases (this is not exactly apples-to-apples: STAR-lite omits the MST entirely since it's deterministic from the data and cheap to reconstruct). More on the pain it addresses [here](https://pckt.blog/b/data-service-diaries/war-on-cars-5xa5v73). The atproto spaces protocol proposes an LtHash set as its canonical data integrity structure instead of a MST: flat key-value with no tree or DAG structure at all to benefit from CAR's CID indexing, fitting more naturally (and without the incompressible CID overhead) into something like STAR. ## Fit with existing primitives STAR-lite builds on DRISL/DASL-CBOR, and uses `varint`-prefixed framing like DASL-CAR. Where DASL-CAR fits DAG-shaped data well, STAR-lite is a more natural fit for flat key-value data. ## Confirm willingness to serve as an editor I confirm! ## Other criteria not covered above Implementation: there is currently a v0 reference [rust](https://crates.io/crates/star-lite) + a third-party Objective-C implementation. I will be adding v1 support to the rust library soon. I think there will be more implementations, especially if it gets adopted by atproto spaces. Community Support: Existing growing uptake of the v0 format, possible standardized use in atproto-spaces, [active evolution](https://bsky.app/profile/bad-example.com/post/3mwc5n4f4gk24) based on feedback. --- Atmosphere post: https://bsky.app/profile/did:plc:lulmyldiq4sb2ikags5sfb25/post/3mwohvqxhpc2h Upcoming CID Congress presentation at https://luma.com/8w8swmx2
Solid Protocol
This document connects a set of specifications that, together, provide applications with secure and permissioned access to externally stored data in an interoperable way.