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.
Tbh, I'm not sure what I'm even doing. Back in the day when I was blogging, very infrequently, my reach was very low. Not sure if I'll have super important stuff to say, but anyway, here we are. Once in a while I might post on Leaflet, because why use just one ATproto blog platform, when you can use two for fun. Or more, if it comes to that. The Atmosphere is all about fun and experimenting anyway. And sometimes talking into the void of the internet.
ATProtocol allows you to build powerful communities with in-built reach, while massively simplifying your website code.
If this week had a theme, it was: *“Congratulations, you now run infrastructure.”* The ATmosphere keeps accelerating toward that glorious point where *everything* is an app, every app is a protocol participant, and everyone discovers (at least once) that blobs are not, in fact, free.
If this week had a theme, it was: *“Congratulations, you now run infrastructure.”* The ATmosphere keeps accelerating toward that glorious point where *everything* is an app, every app is a protocol participant, and everyone discovers (at least once) that blobs are not, in fact, free.
AT Protocol repository sync with Cloudflare Workers built on Tap
AT Protocol repository sync with Cloudflare Workers built on Tap