Proposal: User Intents for Data Reuse · bluesky-social atproto · Discussion #3617

User Intents as Living Data — A Descriptive Meta-Framework

A response to Bluesky's User Intents proposal: instead of prescribing a fixed set of intent categories, treat them as living data and use panproto lenses to map between the vocabularies that different communities will inevitably create.

ATProto User Intents Demo

This is a demo tool which allows atproto accounts to configure a reuse declaration for their public data. You can read more about this atproo mechanism in the "User Intents for Data Reuse" proposal from March 2025. Any account in the atproto network (including Bluesky accounts) can use this tool via OAuth. The source code for this demo is linked above.

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 by dholms · Pull Request #94 · bluesky-social/proposals

This is an initial proposal for permissioned data. Details, terminology, and behaviors are all likely to change. For a friendly introduction to the protocol, check my my Leaflets. For discussion, f...

Machine-readable attitudes - Computational Semantics++

User intent declarations can be viewed as propositional attitudes (permission, prohibition, desire, intention, belief, etc.) over structured descriptions of data use. Treating them that way gives you composable building blocks from existing theory and lens-based translations between community vocabularies that make explicit what each translation cannot carry through.

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.

File Over App: A Philosophy for Digital Longevity

My take on the 'file over app' philosophy and why it’s essential for keeping my data resilient and built to last.

research.latha.org

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

Lexicon Embeds Overview

ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...