Hello, I’m Simon Horrobin. I’m working on a couple of projects which are ATproto relevant… one to handle sport and health data, the other for managing publishing workflow. Both of these need privacy to varying degrees. I think about this in a few axes… who can create, view, edit, delete, grant, revoke, all over time and state.
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
Rashid Aziz: Extending ATproto for private data - ATProto Community
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…
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
The first in a series of posts about major design decisions along the way to a permissioned data protocol for atproto.
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 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.
atproto made simple: granular permissions - underreacted
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
@dholms.at motivated me to make a follow up post on Stratos, @transrights.northsky.social approach to permission data on ATproto! This one is a bit of a brief technical overview and as a nice bonus, I've made the code base public.
Stratos: Lets get Technical
chipnick.com#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)
Emerging from being "down in the technical weeds" of #atproto is a little mashup of @semble.so & WayFinder (wayfinders.network) Semble team released "open collections" this week - here we explore the "private & permissioned data" collection, created by @bmann.ca & now with 3 other contributors
NEW BLOG! After closely following atproto permissioned data, my take: what if an "atproto repository" is the base thing and there's more than one way to sync it? Based on @ipv.sx's take and grounded in a real-world Streamplace use case: how do I make a video private, then public?
What is an atproto repository?
iameli.leaflet.pubPrivate & 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
