if there's one good thing to have come out of node.js' arguably messy esm rollout, it'd be resolve conditions i can write node.js-optimized functions without it spilling over to the browser
node's internal buffer methods for writing and reading utf8 is faster than textencoder/textdecoder
ff7 ass image RE:
allocUnsafe my beloved
[music.youtube.com/watch?v=jK4RRu…]( ) [えりあし]( )
watch as atcute becomes a monorepository of packages that are only tangentially related to atproto
[github.com/denoland/deno/…]( ) here is hoping [`node:crypto` implementation d...]( )
pls package maintainers dont minify your library output it makes patching very annoying
i prefer using ast factory functions for doing codegen instead of rawdogging template literals, but pulling in a codegen library like astring hurts me for some reason ...maybe i should write my own ecmascript codegen?
good news i am no longer running into oauth jti error maybe using uuidv7 for jti did it