Post

Bailey Townsend 🦀
@pds.dad

If you’re curious how they nerd sniped me into joining npmx to help, it was this. Lots of interesting questions of how can you integrate atproto beyond things like bluesky comments on a website if the application is not inherently atproto? Hoping we can find some good answers to these questions.

patak@patak.cat

adding social features to our websites will accelerate atproto adoption faster than building pure atproto apps

5 reposts70 likes

đť•®
@chrisshank.com

One of my thoughts atm is that separating read (material) from write (instrument) would make parts of atproto more composable, and thus embeddable. bsky.app/profile/chri...

đť•®@chrisshank.com

Imagining atproto as a post-app protocol starts with materializing the social filesystem – decomposing apps and their data into materials and instruments. For the time being, this guestbook is a good example where the display element is a material and the sign element is an instrument.