hayleigh @hayleigh.dev · 20/08/2026fyi you're still mailing out copy from the last event, might want to fix that up in case folks accidentally head to grenwich! 110
hayleigh @hayleigh.dev · 29/07/2026what i see right before i read something that instantly pisses me off 0141
hayleigh @hayleigh.dev · 21/07/2026ignoring the fact the code is literally The Worst, i thought building a lexgen cli would be a good way to dogfood `at` its not much but working out how to resolve the actual lexicon json just from the name was pretty satisfying 😌 2360
hayleigh @hayleigh.dev · 20/07/2026here is the published spec, and here is the official implementation: ``` const documentData = z.object({ did: z.string(), rotationKeys: z.array(z.string()), verificationMethods: z.record(z.string()), alsoKnownAs: z.array(z.string()), services: z.record(service), }) ``` 120
hayleigh @hayleigh.dev · 23/06/2026hmm 🤔 but thats alright, if you drop me an email at few_joinery.9v[at]icloud.com i'll forward it to my actual address ^.^ 110
hayleigh @hayleigh.dev · 27/04/2026whether or not you care about that.. i think it would be good to be more-consistent with how you style border accents in general, you effectively have three different variations of this effect 130
hayleigh @hayleigh.dev · 27/04/2026this is a very specific nit but if this design system hasn't been vibe coded (and you don't want people to think it was) then you might want to rethink this left-border-accent-colour thing. LLMs absolutely love this particular effect and i know some people will be put-off by it. 130
hayleigh @hayleigh.dev · 03/02/2026Is the raw data available anywhere? I'd love to see some of those "other answers" 👀 110
hayleigh @hayleigh.dev · 30/01/2026Huh that's so weird, none of my tickets for sncb look like this at all 🤔 as long as it has the qr code im very confident it'll be fine though! 010
hayleigh @hayleigh.dev · 11/01/2026in our benchmark we're now comfortably beating react and among the fastest options when using `element.memo`. if performance concerns were one of the things holding you back from trying lustre, well.. they shouldnt! github.com/lustre-labs/... 0243
hayleigh @hayleigh.dev · 09/12/2025well holy shit we only went and did it???? it was only last march that i started to work on lustre "seriously". since then we've average ~100 stars a month, have a bunch of companies using it in prod, and so many kind words from folks 🥺 i guess i better work on a 5.5 release now! 1330
hayleigh @hayleigh.dev · 07/12/2025all i'm saying is if we average 5 stars a day lustre can hit 2k in time for my birthday 🥺👉👈 thatd be pretty cool huh huh what if i promise a release when we hit 2k 👀 github.com/lustre-labs/... gogogogogo 23710
hayleigh @hayleigh.dev · 19/09/2025renata has been on a warpath recently, she's released a bunch of really good libraries and shipped two real-world sites with gleam/lustre go give her some love github.com/renatillas renatillas.pages.dev 180
hayleigh @hayleigh.dev · 19/09/2025i've not even released clique yet and someone is already using it to build out their personal site!! the gleam community is just built different i swear 2266
hayleigh @hayleigh.dev · 12/09/2025Update on my reactflow ripoff, we have properly functional handles and connections! I think almost all the fundamentals are here enough to publish a v1. Before I do that it's time for a round of docs and polish ^.^ 2250
hayleigh @hayleigh.dev · 09/09/2025cracked itttttttttt, the html for this is killer too like: <clique-viewport> <clique-edge-renderer> <clique-edge from="a.out" to="b.in" type="bezier" /> </clique-edge-renderer> <clique-node id="a" x="0" y="200"> <clique-handle name="freq" /> </clique-node> </clique-viewport> 1110
hayleigh @hayleigh.dev · 09/09/2025tonight i added panning inertia and rewrote how the core rendering works, i'm super pleased. that's the fundamentals down i think, tomorrow is on to all the events required to implement real things. first up is connecting handles together. 1221
hayleigh @hayleigh.dev · 07/09/2025Earlier this year I left @xyflow.com to, among other things, spend more time working on gleam and lustre. it was a bit of a running joke that eventually i'd make a lustreflow fork... i'm still a long way off but i'm giving it a shot and already have the basic pan/zoom/nodes/edges canvas down! 5350
hayleigh @hayleigh.dev · 19/04/2025the @gleam.run community is made up of some of the most incredible trans folks i know. even when it feels like the rest of the world is stacking up against us, gleam will always be a safe space. come join us! 💕 0349
hayleigh @hayleigh.dev · 19/04/2025We've written a BUNCH of examples to help people get on their feet quickly, there's over 20 now and we'll be adding more over time! hexdocs.pm/lustre/refer... 140
hayleigh @hayleigh.dev · 19/04/2025We rewrote the entire vdom from scratch, and now we're way faster than we used to be. Fast enough that we compete with latest versions of Elm and React. Which is great news for me because it means I can never think about this again, and neither do Lustre users now ^.^ 160
hayleigh @hayleigh.dev · 02/02/2025Creator of @gleam.run talking about SQL for some reason, weird 1361
hayleigh @hayleigh.dev · 14/01/2025They already made concessions on the home page. We need to push harder ✊ 130
hayleigh @hayleigh.dev · 14/01/2025The only way I'm going to convince @codebeam.bsky.social to update their promo materials is if I bring an army of gleamlins to SF. If you've missed what we've been up to the last year you've missed *a lot*. You can still grab an early bird ticket and listen to me yap about it 👀 codebeamamerica.com 2171
hayleigh @hayleigh.dev · 27/11/2024Unironically stuck buffering on gleam, its a sign from the gods. 220
hayleigh @hayleigh.dev · 18/11/2024As part of my ongoing effort to follow @codesync.bsky.social around the playground until we're best friends, I'll be speaking at #CodeBEAMAmerica next march 🎉 Gleam has had a super busy year since we released v1, so I'll be giving an update for all y'all that haven't been paying enough attention 👁️👁️ 2255
hayleigh @hayleigh.dev · 18/11/2024I'll be honest elm really fumbled the bag by not having nested TEA. Building components at this abstraction level with lustre has been an absolute *joy*, here's the message type for this accordion. It's just so explicit, we can see all the interaction up front; its great! 170
hayleigh @hayleigh.dev · 18/11/2024✅ Accordion... - each item navigable in the page tab sequence - up/down/home/end keyboard navigation - "multi" mode allows many items open at once - "exactly-one" mode prevents collapsing 2221
hayleigh @hayleigh.dev · 17/11/2024so we can tweak things like radius, spacing, and colours trivially by modifying the theme, for example! 010
hayleigh @hayleigh.dev · 16/11/2024lustre/ui is built around a theme system so it's also pretty easy to add your own visual identity to these components, and themes can be scoped to a css class or data attribute so its possible to have multiple themes on a page if you need that for some reason ^^ 1110
hayleigh @hayleigh.dev · 16/11/2024lustre/ui also has dark mode support out of the box which is honestly super slick tbh 170
hayleigh @hayleigh.dev · 16/11/2024Here's a little status update with what I have for lustre/ui so far, with a few others not shown here ^^ Unlike the tailwind trend these days, all the css for lustre/ui is lovingly hand-crafted so even if you change *nothing* you might stand out a little against the 100s of shadcn drop-ins 💕 6506
hayleigh @hayleigh.dev · 08/11/2024Super exciting to see Elixir's research into static analysis already paying off in the real world (whoda thunk it?)! I do worry that types like `dynamic(false or {term(), binary()})` are going to alienate some people though github.com/phoenixframe... 2265