Post

implementing atproto oauth got me dizzzyyy 😵‍💫 because gleam supports two targets with different concurrency methods the preferred approach is "sans-io" where the api doesnt perform async operations directly but instead exposes functions to construct requests, decode responses, etc...

1/8/26, 8:09 am1 repost28 likes

hayleigh

@hayleigh.dev

1 Aug

this isn't the worst but for a multi-step flow like oauth its a little trickty to get something nice. then throw in the fact that all crypto in js is async and we're really fighting to get an api that feels nice to use 😭

hayleigh

@hayleigh.dev

1 Aug

also like, im so frontend shaped, i should not be here someone send help

Mar !!

@strawmelonjuice.nl

1 Aug

YOU COULD'VE BUT YOU WENT THE ARMS RACE WAY

dw i still love u <3

y'all did oauth already??

rebecca~

@becca.monster

1 Aug

minutes before implementing peters effect interpreters

hayleigh

@hayleigh.dev

1 Aug

im being very zen about it actually

luci

@punkrockweb.dev

1 Aug

I've been relearning gleam and trying to learn atproto (beyond just the high-level concepts) by trying my hand at writing a PDS and its so much! and the specs can be so vague! (I'm not very far along, I've got like, a mostly working CAR parser)