charlotte πŸ‡

charlotte πŸ‡

@char.lt

charlotte or cinnamon. 25 ^-^ computer programmer & music producer spamposting account @plushie.holdings en/fr/ν•œ/es OK

5.4K followers411 following2.6K posts

@cerulea/lexicon is now up on JSR. it's a library for defining lexicons *in TypeScript* (the schema code generates the schema doc, instead of the other way around as with `@atproto/lex` et al) and you also get a nice record validator/builder API at the same time

the backlinks.cerulea.blue prototype is currently using 40gb of on-disk storage and about a terabyte and a half of object storage. i basically never have to take it down to swap out a disk and it'll scale linearly with time ^-^ this is reasonably cheap and hands-off full network indexing

i wrote a list of some software talks that i think you should watch if you're the type of person who enjoys that. they're all mostly about the metaphysics of simplicity and the weight of the practice. one of them is about a common pattern that appears between disciplines. they're all excellent

charlotte πŸ‡ reposted

i caved and wrote a little jj primer. it mostly outlines a mental model for what's going on inside jj and then defers to a Real Tutorial, but i think it'll be useful char.lt/blog/2026/07/jj-vcs/

char.ltcharlotte's jujutsu tutorial - Charlotte Soma little primer on becoming a version control hipster

thinkin about how i would structure charlotte's jj tutorial low key

broken record ik but it's very unfortunate that this is set in past tense when PDS -> app service proxying is key to actual use cases of altering undesired app behavior today (e.g. age assurance circumvention, feedgen sponsored item elision, etc)

P(aul) Frazee@pfrazee.com

So anyway, one of those early ideas was that by proxying through the PDS we created similar benefits to having an extensible browser. Rerouting or blocking requests to alter application behaviors, things like that. The logic was to act as a political backpressure to the applications

just doesn't feel like skipping one header on the client and targeting the url straight at the app server is a DX benefit big enough to justify ceding control from infrastructure the user controls to opaque (unchangeable!) territory of the future adversary, even if u do get to do serverside RYOW

feels much less ulysses pact feels much less locked-open when the app server can just go "yeahhh well im gonna keep ingesting this data u give me but i wont keep writing records to PDSes because i got a competitor trying to adversarial interop me"

i don't really know what to post on main i'm having lots of fun lately but not really working on software or music which is kinda what i wanted to distill down to on here

View full thread

i just did sync.listBlobs, repo.uploadBlob, and sync.getBlob :) my sync.getBlob implementation also differs from the vanilla implementation in that it supports the HTTP Range header and can return partial responses

things it has this Tuesday night: - OAuth authorization_code flow - repo.getRecord things it doesnt have: - putRecord - sync.getRecord - getRepo - subscribeRepos

about to sit on trains for five hours and the price is a superposition of Β£70 and Β£0

November Kelly@postoctobrist.bsky.social

the funny thing about train travel in the UK is that it’s both extremely expensive and also free. I don’t think I’ve had a single journey this year that wasn’t so delayed I got a full refund