ahhhhhhhh RE:
i wish lexicon had syntax so it wouldn’t be embarrassing to post it. whenever i see that pile of json i want to scrub my eyes
i think reddwarf is a fascinating experiment in that it shows how flexible AT is. you can be β€œserious” about performance and put everything into a database and so on… or you could just hit the source and assemble the data from wherever it lives on the go. being able to do both is wild RE:
with [@slices.network]( ) and [@microcosm.blue]( ) Constellation offering easy indexing on the atmosphere, we’re getting close to a point where forks of the official bluesky client can augment it with non-trivial new features without running their own backend
i wrote down the process of resolving an at:// URI step by step. turns out, it's a great way to learn how the AT protocol works! [Where It's at:// β€” overreacted]( )
πŸ‘€πŸ‘€πŸ‘€πŸ‘€πŸ‘€ RE:
this api is weird but i’ve really enjoyed the mental model it offers. i highly recommend every react developer who struggled with effects to play with it and to get a sense of when it’s useful RE:
[@ives.sh]( ) halp, it seems like sandpack isn't resolving 19.2 at all when used from react site, why could that be https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreib3vlgy6mzwdzec4377oejpenidcrfzmgcsdvhsm7hmiqh5cqtkx4
hey chat if i want to use "atproto" in a Title Case Context, does it stay "atproto" or does it turn into "ATProto" or do i have to do the whole "AT Protocol" thing
one exciting thing about this is that you will soon be able to create an atproto app (with real data!) comfortably within a time slot of a conference talk RE: