







An open protocol for per-user storage on the Web
The local-only web
In this post, I explore the potential of the File System Access API to create local-only web experiences. I discuss how this API, combined with tools like Logseq, allows for on-device data storage outside the browser sandbox. While exciting, I also acknowledge the current limitations, such as the need to re-grant file access on refresh, the lack of a visual indicator for local-only sites, and the difficulty of preventing data exfiltration entirely. Despite these challenges, I believe this area holds significant potential and deserves further exploration.
Wildland (@WildlandIO) on X
An open protocol for data management that allows users to have sole ownership of their data. Join us! https://t.co/AqwplMcG9u Developed by @GolemFoundation

Persistent Storage Options
This API provides database persistence via localStorage/sessionStorage and, in compatible browsers, the Origin-Private FileSystem.
Three schemes for shared-private storage - Paul's Leaflets
Linked Web Storage Use Cases
User stories and use cases for the Linked Web Storage (LWS) spec.
Abstraction Begets Fragmentation
Christian Heilmann raises the ugly issue of offline storage. LocalStorage’s synchronous nature makes it slow, WebSQL is deprecated, and IndexedDB’s API induc...
Locking the Web Open: A Call for a Decentralized Web | Brewster Kahle's Blog
(Short form article, Short lecture, Long lecture, demo of a fraction of the idea of a distributed website (or paste this link in maelstrom))
AT Protocol PDS
Explore this self-hosted AT Protocol Personal Data Server (PDS) with useful links and details.

Willow - Willow’25
Peer-to-peer protocols which scale up, down, and sideways. Sychronisable data storage, fine-grained access control, private and efficient synchronisation, and secure data delivery by any means possible.
Social Network User Data Storage
Social Network User Data Storage
Social Network User Data Storage
ATProtocol: Data Ownership for the open social web
A practical AT Protocol architecture deck for platform developers.
Once again looking at bring your own user-data storage options (for my malleable software experiment this time). What do people think are some user friendly options that don't require any OAuth apps to be created on the server? ie. no Dropbox, Google Drive, One Drive & other services like that.
new data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)
Permissioned Data Diary 5: What’s in a Name?
dholms.leaflet.pub