Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does - Nick's Blog
AT Protocol is public by default. Everything you write goes into a signed, archived, and rebroadcastable repository that anyone can read from and moves throu…
Rashid Aziz: Extending ATproto for private data - ATProto Community
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...
Guide for migrating your app to atproto
This is a quick response to this post @anniesexton.com on Bluesky Please do edit and point to other resources If you have an existing database powered app, here is a rough guide to thinking about migrating to atproto Figure out which data is private, this will stay in your database Figure out what the main data is. Look around for an existing lexicon or create your own. When creating new records, write them to the user PDS. You’ll need to start aggregating your lexicon types from the ne...
Permissioned data on atproto — pick your depth
A private room in a place with no walls: how engineers are adding permissioned data to atproto. Read it plain-language or technical.
Mostly withholding judgement on @attie.ai but an important question for me that I haven’t seen asked: Are the primitives atproto records? Will the non-public parts be stored in permissioned repos? Can I ship an Attie competitor that uses all of the users’ same data without touching Attie itself?
#atproto devs, I know data is public and accessible But we need more tools to help people download their data in *familiar and user-friendly* formats Data ownership is also about enabling people to use and move their data in whatever way they desire, even if they wish to take it outside the protocol
Victoria
I'd argue that having an export tool to fetch the data from the PDSes into familiar data files would be very much appreciated by the general public, both webcomic authors and readers (especially converting the block content into something clean to import anywhere they might desire)
This is a radically different idea than the advocacy I’ve seen for “data portability” and ”data sovereignty”. It’s a *restructuring* of power rather than small adjustments to existing structures. atproto and local-first, both in their own ways, demonstrate what such a restructuring can look like.
Orion Reed
We need to structurally separate user data from applications so that applications become *users* of data rather than *containers* for it.
What if permissioned data but then public though
Transitioning data from permissioned to public?
discourse.atprotocol.communityIs this a thing? Something about private data on AT Proto, where a person could purchase content and have a copy of said content injected into their Private Data, so it could not be removed without their consent? I’m thinking “I’ve bought a copy of a book, and now the book blob lives in my PDS”
Private & Permissioned Data
ATProto Private & Permissioned data
opensocial.group/proposal
Atproto spaces alpha updates
Habitat's road to release: 06 commenting - building [at] habitat
Arbiter Progress Report 4 - Zicklag's Leaflets
Arbiter Progress Report 3 - Zicklag's Leaflets
Arbiter Progress Report 2 - Zicklag's Leaflets
