does anyone have tips for doing skew protection (described in [station.railway.com/feedback/dep...]( )) when self-hosting Next.js? i think i'd like to keep two deploys alive at any given time, and have the app autoreload on first build mismatch server action or something like that [Deploy skew protection - Railw...]( )
i just walked "check out sidetrail" by @npub1up3t...czka [sidetrail.app/@danabra.mov...]( ) [check out sidetrail]( )
today's progress on my toy app: asked claude to set up otel (i've never used that before). took some iteration but i have a graphana dashboard with P90/P99 responses, error rate, traces >150ms, and all recent traces. that's nice
i sort of dislike bun for similar reasons but i think more guardrails is actually better for llms too. if anything, type checkers, borrow checkers etc can get a lot more brutal RE:
cache components is very very fun to play with. i'm a big fan. one thing i'm not sure about is whether to place "use cache" closer to the data layer (particular queries) or ui layer (particular component trees). obviously could do both but i wonder which pattern i'll gravitate towards
i thought stranger things season 5 so far was actually very good. it’s obviously a different series to the first season, which everyone keeps harping on about. but imo it’s the first time since season 1 that the series has found its groove again. im excited to watch it go out
one annoying thing about "log in with atproto" is that it's not a single button press because you have to enter the handle. whereas with google account it's just a button press and then another button press to choose the account i'm logging into. is there a solution to this?
psst @npub19qkm...vn3j @npub1xfe0...cn4d this might actually be a really good one for engagement RE: View quoted note β†’
my experience this weekend - did a few successful wild refactors (completely swapped data layer and removed a bunch of third party code, completely new end-to-end test suite) - reduced a very tricky bug to a minimal repro mostly autopilot but my feedback was absolutely crucial at every stage RE:
spent the last day fighting a gnarly issue (bug?) in how Next 16 Cache Components interact with atproto OAuth flow (cc [@matthieu.bsky.team@bsky.brid.gy]( )). might be a Next bug or not, anyway i filed [github.com/vercel/next....]( ) [Cache Components causes fetch ...]( )