mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
abf99d05fc
Restructured from flat .tex/.pdf files into per-paper subdirectories. Added Antje Worring as co-author on all papers. Synced PDFs to pdfs/ for download site.
47 lines
2.2 KiB
TeX
47 lines
2.2 KiB
TeX
\section{Related Work}
|
|
\label{sec:related}
|
|
% ============================================================================
|
|
|
|
\paragraph{Solid (Berners-Lee).}
|
|
Solid~\cite{solid2016} proposed personal data pods where users store their data
|
|
and grant applications access. The Capsule model shares Solid's vision of data
|
|
sovereignty but differs in three ways: (1) Capsule vaults are encrypted at rest
|
|
(Solid pods are not); (2) sync is CRDT-based rather than LDP-based; (3) trust
|
|
is anchored to a blockchain rather than relying on WebID-TLS.
|
|
|
|
\paragraph{Fission (UCAN).}
|
|
Fission~\cite{fission2021} introduced UCAN (User Controlled Authorization
|
|
Networks) for decentralized capability delegation. The Capsule capability set
|
|
$\Gamma$ builds directly on UCAN semantics. The difference: Capsule capabilities
|
|
are enforced on K-Chain, providing revocation guarantees that pure UCAN
|
|
(off-chain) cannot offer.
|
|
|
|
\paragraph{Ceramic.}
|
|
Ceramic~\cite{ceramic2020} provides mutable data streams anchored to a
|
|
blockchain. Capsules differ by storing data locally (not on IPFS), using
|
|
SQLite (not JSON streams), and supporting offline-first operation without
|
|
network access.
|
|
|
|
\paragraph{DXOS.}
|
|
DXOS~\cite{dxos2023} builds local-first collaborative applications with ECHO
|
|
(Eventually Consistent Hierarchical Objects). The Capsule CRDT sync model is
|
|
closest to DXOS in spirit. The distinction: Capsules add a formal trust kernel
|
|
(Lux) for identity, key policy, and threshold operations that DXOS handles
|
|
through simpler peer-to-peer key exchange.
|
|
|
|
\paragraph{Local-First Software.}
|
|
Kleppmann et al.~\cite{kleppmann2019} articulated seven ideals for local-first
|
|
software: fast, multi-device, offline, collaborative, long-lived, private,
|
|
and user-owned. The Capsule model is a concrete architecture that satisfies
|
|
all seven, adding the trust kernel that the original manifesto identified
|
|
as missing.
|
|
|
|
\paragraph{Evervault.}
|
|
Evervault~\cite{evervault2022} provides encryption-as-a-service with relay
|
|
proxies that encrypt data before it reaches application servers. Capsules
|
|
subsume this pattern: the vault is always encrypted, and providers never see
|
|
plaintext. The difference is architectural---Evervault is a middlebox;
|
|
Capsules are a runtime.
|
|
|
|
% ============================================================================
|