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/...](
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
), in particular embeds (to other trails, to bsky posts, and external links) should no longer be "jumpy" when they load
unlike with "native" bluesky iframe embeds, i'm doing resolving on the server so it's immediately available if the data is cached
i don’t get the coverage that says meta is putting brakes on “metaverse” while at the same time saying they’re increasing focus on glasses. aren’t glasses literally the endgame of that specific project? ie to be apple/google of next computing platform.
) when you click on actions that require auth, should be fixed now
