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.
Proposal: User Intents for Data Reuse · bluesky-social atproto · Discussion #3617
This is a discussion thread for the User Intents for Data Reuse proposal.
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.
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...
Small models, big results: Achieving superior intent extraction through decomposition
We present a novel approach to tackle the task of understanding user intents from UI interaction trajectories using small models, which shows better results than significantly larger models.
Modeling communities on permissioned data - Daniel's Leaflets
Arguing against "universal spaces" and raising a couple questions that come up as a result.
Permissioned Data Shapes: Community-Moderated Content - Nick's Blog
A community can own spaces the way a person does: a club's members post to each other under a dedicated community DID, with a feed space for content, a moderation space for notes, a labels space for filtering, and a single app view as the only window into any of it.
Bonsai: Intentional and Personalized Social Media Feeds
Social media feeds use predictive models to maximize engagement, often misaligning how people consume content with how they wish to. We introduce Bonsai, a system that enables people to build personalized and intentional feeds. Bonsai implements a platform-agnostic framework comprising Planning, Sourcing, Curating, and Ranking modules. This framework allows users to express their intent in natural language and exert fine-grained control over a procedurally transparent feed creation process. We evaluated the system with 15 Bluesky users in a two-phase, multi-week study. We find that participants successfully used our system to discover new content, filter out irrelevant or toxic posts, and disentangle engagement from intent, but curating intentional feeds required more effort than they are used to. Simultaneously, users sought system transparency mechanisms to effectively use (and trust) intentional, personalized feeds. Overall, our work highlights intentional feedbuilding as a viable path beyond engagement-based optimization.
A folksonomy of lexicons - Chris's Corner
On the design and intent of different lexicons
Building a Privacy Preserving Intent-Driven Discovery Protocol
There are a lot of architectural bits, but if I had to pick one design feature it's Lexicons. Lexicons allow for new shared data types and structures in a way that are immediately available on network for any other service provider to adopt. Getting shared agreement in ActivityPub is hard.
Pedro Vezza
Why did you decide to bet on atproto over Mastodon or similar?
I've been thinking a lot lately about how lexicon authors could help app developers understand intent. #atproto trezy.codes/blog/what-if-lexicons-knew-ho…
What If Lexicons Knew How to Look? - A Thought Experiment About Display Intents on the Atmosphere
trezy.codes
winter
has anyone thought about the multi repo feed yet or are we still in the era of "this is a <app.bsky.*> viewer" and "this is a <site.standard.*> viewer"
Bluesky is scared to commit to making a universal app that works with any atproto lexicon. I am not. And am pretty committed to our social-app fork being able to work with more and more content types (short video, fintech, blogs, music, etc.) Acorn customers get this for their communities too.
Richard Ferro, MD MSc
Also, will any platforms using acorn have access to these integrations as well?
I know I’ve said this before and recently, but I’m over the skeuomorphic UX of Bluesky that makes it look and feel like a 20 year old social media app. I’m ready for new experiences for this kind of media/data. This information architecture is played out. Let’s try some new ideas with other clients.
this is my preferred pattern for atmosphere apps that are wanting to ”reuse” or “integrate” the bluesky social graph/lexicon don’t make me automatically follow everyone i follow on bluesky, but make it easy to find/discover/import my bluesky social graph (or other social graphs) on my own terms
dame
yeah i really like this, though it would be nice to be able to quickly “discover” users you follow on bluesky who also are active on grain and quickly follow them @chadtmiller.com
