Tynan Purdy ⁂
@tynanpurdy.com
ok this gets me thinking, one could disguise features as other features. Like a 'feedback' form in an app could actually just write an issue on the tangled repo for an oss app
dame
i wanna be able to add an issue to a repo on @tangled.org without ever leaving the bluesky client maybe i should add this to @anisota.net eventually, some other clients could as well
Jan 11, 2026 at 1:28 AM
userinput.app
Collect feedback: post ideas, vote on what matters, and watch them go from planned to shipped.
Apps are too complex so maybe features should be ownable and tradable
Posted on Friday 29 Apr 2022. 1,955 words, 12 links. By Matt Webb.
Permissioned Data Shapes: Notifications - Nick's Blog
A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.
A little step: working on an AppView and small Lexicon to make contribution information modular and transparent - so it is easier to signal if you're looking for support, and how to provide it; will have the repo public soon, and hope to get the alpha public later this week - feedback welcome!
i wonder how much of this can be prototyped in userland with no new ui eg just a thing that creates “collection” accounts operated by bots. curators can post stuff there by dm’ing the bot. as a reader, you follow the account, so naturally it plays into your Following and For You etc
dan
“semble for bluesky inside bluesky app” is a good way to articulate exactly what i’m missing in the product. custom feeds are like half of that but they’re a readonly interface
This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
Wouldn’t it be cool if your link created minimized version of this as an embed in the post so the most essential info is immediately available? Could even be interactive. (Drawing attention to it since this sort of cross-app discoverability feature seems to be a core part of the 2026 roadmap.)
I’ve put atmospheric feedback in @standard-reader.app and it’s been amazing! - @userinput.app for feedback - @atstore.fyi for reviews Read about my approach 👇
Atmospheric Feedback
hipstersmoothie.comToday's example of #AtmosphericUX Designer of one app identifies a scenario where it'd be worth capturing data to appear properly in an otherwise unrelated app All that's required is a one-post explainer of the tiny lexicon record to write + they're sharing data directly Zero integration code!
Joe Basser
@montoulieu.dev any documentation or advice on creating @beaconbits.app check-ins from an atmospheric ticket scan? 👀
What's the intended app/user etiquette for atproto apps with regards to publishing to the same lexicon? Like, say I build an atproto app, would it catch users by surprise if the wrote to the same records (e.g. posts, likes, etc?) that show up in the bsky.app? Or should my app be isolated?
