Post

I like these but they also end up implying that all AT Protocol clients are for social posts. npmx is technically an AT Protocol client and definitely isn't for social posts.

I think ATproto works for all ATproto users and usages: social and not social. "ATproto social client" if you want to fine-grained it, but might I wouldn't go down that rabbit hole. Does still sound good tho.

the reason I'm asking this question is because IMO users should have choice when they're clicking a link to an app.bsky.feed.post link and right now the ecosystem default is to just link to Bluesky I should be able to set a record and have apps open in mu.social or Blacksky rather than Bluesky

web intents but for atproto. Connecting which lexicons an app can read as part of an app catalog has been discussed. Things like @atproto.at can read ALL lexicons, but regular users aren't going to want to "view source" Related: webtil.es has some of these concepts inside of it

webtil.esWeb TilesTiles are composable web docs and apps that can safely be used in arbitrary contexts and assembled from multiple sources to carry out complex user interface tasks.

0 reposts2 likes

No replies yet.