this sounds corny but atproto is basically the internet of json
what is the best practice for when to reach for a strongRef, as opposed to a ref? is it basically "if you really want to make sure it's linking to the same version"? is this up to the app to decide what "deserves" this guarantee? e.g. a "like" wants to be concrete but sometimes you don't mind edits?
i keep using [playground.typelex.org]( ) just to look up lexicons. is there any site that does this with good autocomplete? ideally i want a big search box like google, i type "app.bsky post". it suggests "app.bsky.feed.post" (partial match). pressing Enter shows lexicon definition + example from shape
that's actually a really fun benchmark, watch the next 20 seconds (timestamped) [React Conf 2025 Day 1](https://www.youtube.com/live/zyVRg2QR6LA?si=rq9xUZuZTdgDAAnS&t=20455 )
would be cool if @npub10vgn...h0np had "shouts" too
honestly i think there was something about the google reader shutdown that in retrospect was a turning point both for google itself and for the broader internet RE:
reader. great naming choice. reminds me of something RE:
challenge accepted. may i present my submission: [codepen.io/gaearon-the-...](https://codepen.io/gaearon-the-encoder/pen/YPwYPye ) RE: [Untitled](https://codepen.io/gaearon-the-encoder/pen/YPwYPye )
tag game on atproto. self record lexicon: { tag: did } then we can follow the chain from any starting point. you can see where each sequence of tags resolve from any person to the last one in their chain. or back global tag graph is visualized. people can edit their records, redirect, add loops
the strangest thing about vibe engineering so far to me is that i constantly have to recalibrate my intuition about how much time something will take