uhhh. what https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreibdn6ph6tnpqcbmr45eg5sh6hg2sb4w37dlenlqdzlqb4j3i33zuq

i’m finally watching paul mccartney in space and it’s good

should’ve called them API components View quoted note →

llms enabling new modes of perf debugging. just figured out an annoying safari unexpected relayout by passing traces to claude which calculated events/layouts ratio to verify theories the more structured data it can access the better the results

shipped a bug yesterday that showed error screen instead of login screen on sidetrail.app when you click on actions that require auth, should be fixed now

i wonder if it could be because my local dev env without PRIVATE_KEY_ES256 at some point inserted a session into prod db (while debugging)

okay so uhhh does anyone know why my code would trigger this oauth error in the refresh flow? this is from atproto node oauth client. my setup: tangled.org/danabra.mov/... logging out and in worked but wtf cc @matthieu.bsky.team@bsky.brid.gy https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreif7lo477octienjqdwkk3plbrqr7msu2sqiuzjecbgj2kttureeaq

seeing some weird oauth errors i don’t understand in server logs. if sidetrail doesn’t let you perform any actions, try logging out and back in, and that should fix it. i’ll have a look tomorrow

i should make a next.js course