private/permissioned data on atproto

Your files. Your account.

AT Storage keeps exact media originals in an owner-only permissioned Space, organizes them into albums. Other file types will be added soon™

The Atproto Spaces Alpha is Live - AT Protocol

Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.

Habitat's road to release: 02 sap for syncing permissioned spaces - building [at] habitat

A package to help apps keep permissioned data up-to-date.

Gradients of intimacy and creating shelter: An interview with Erin Kissane

How might we use nature as an inspiration for creating online communities?

The Vault: a (possible) answer to the "Fully-Private Community Data" question

Oh yeah, I should clarify that I totally expect a community DID to have a repo and in some cases, it makes sense for that repo to publish community-owned data. Just as a baseline, I think it’s good for most social activity to happen in a repo without needing to interact with the community’s repo. Even in the cases where a community DID wants to “pull in” some user content, I think it’s better for it to do it non-interactively with the user. For instance, publishing its side of things after syn...

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.

Habitat

A unified layer for your organization's data.

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.

science.latha.org

A permissioned appview for scientific documents on AT Protocol. True data ownership with optional monetization.

inspo.land

Permissioned Data Interlude: Spaces - Daniel's Leaflets

In which I retcon the naming of everything.

calendar pt. 1: ATProtocol beyond AppViews - building [at] habitat

our approach to permissioned data (part 1!)

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.

Licensing terms for data in the Atmosphere

I’d like to raise a fun and interesting topic, and that’s intellectual property and content licensing. The data that flies around the Atmosphere is all visible and public. We’re at a stage within the Atmosphere where services are beginning to grow, and we’re beginning to see lexicons and data that express creative works that extend in length beyond microblogging. I think that the Standard.site lexicons are a great example. But these creations lead to further questions. Who has permission to...

but should apps see our data? - building [at] habitat

thinking small on the protocol

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.