Continuing from my previous leaflet on private data, I want to explore three broad schemes for shared-private storage that I’ve seen emerge in various propos…
Private, non-shared data in repo? · bluesky-social atproto · Discussion #3363
I have a use-case for keeping private data in a repo, i.e. data that does not leave the repo via the standard sharing mechanisms, and before I leap into modifying the code to support it, I'd li...
[Proposal] Shared private Data for social posting
seconding a sidecar private PDS endpoint attached to the DID document as a good approach in the general case (in an implementation of private data I did which never saw the light of day, this was the approach I took), though obviously it imposes additional constraints on a first mover building this out.
Private Chat Backups with Local-First Principles
Introducing encrypted chat backups and multi-device syncing that extends our end-to-end privacy principles to persistent cloud storage.
Permissioned Data Diary 2: Buckets - Daniel's Leaflets
The second in a series of posts building up a solution to permissioned data on atproto. We introduce buckets: a new protocol primitive for creating a shared social context.
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
A self-only space is the smallest shape permissioned data can take: one authority, one member, one repo, and private bookmarks that share a record shape and a write path with public ones.
Persistent Storage Options
This API provides database persistence via localStorage/sessionStorage and, in compatible browsers, the Origin-Private FileSystem.
Rashid Aziz: Extending ATproto for private data - ATProto Community
Playing with Parlances - Permissioned Data & AT Protocol - AT-WayFinding
Community privacy is one of our top priorities at @transrights.northsky.social which isn't possible out of the box with any ATproto implementation today that doesn't just hide an entire PDS. We're developing in the open and so I've published a proposal on it, feedback as always is we
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.
I was looking at an older version of the software I'm yet again working on from what, 15 years ago, and I can't believe we're still mostly stuck with the same private blob storage options that can serve as user-data storage. S3-compatible storage + Dropbox was the list: github.com/icidasset/ongaku-ryoho-v1?tab…
private data unconf session at #atmosphereconf is packed really great to hear about the different approaches, use cases, concerns we don't have great language for describing topology and trade-offs in distributed architectures the "what is where, and why" often feels untangling vs compositional
At @roomy.space we've been cooking up the design for the next, ATProto-native iteration of Roomy, and that includes private data on protocol! The first component that we're working on is a group membership service that we're calling the "arbiter". Here's full overview of the design so far!
The Arbiter - Group Management for Permissioned Spaces and Beyond
zicklag.leaflet.pub
