GitHub Stars
GitHub stars posts
1837 posts
latest post 2026-05-01
Publishing rhythm
I like the charts that Theo brings to to these videos. Shout out for a positive k8s reference and not shitting on it.
Htmx brings html/css just a bit further down the complexity graph with little to no extra effort, while react allows us to go all the way full complexity at the cost of build and dev complexity to go from zero to 100 as soon as its introduced.
htmx brings us back to the ease of jquery ajax without any complex swapping or json parsing, all of the object parsing and html templating is done in the backend, the front end just tracks where to put it. HTMX couples the frontend and backend much tigher, since all of the front end html is generated in the backend, done correctly it is not possible for the front end to get out of sync and try to do things that the back end does not know how to handle, vice versa.
It’s interesting how many people in tech maintain a blog. I think part of this brings us back to web 1.0 days when so many individual websites owned the web it was a free for all unindexed land and you got to own a small piece of it.
I agree with most of Brittany’s points here I write a lot to keep my skills sharp, and to refer back to. Brittany mentions keeping all her old posts, even the cringy ones. I’m all with you here, I’m just wodering how you look back at anything you wrote in the past and not get a bit of that feel, maybe its just me, but I see cringe and mistakes gallore, but it all makes me better moving forward.
nice overview of availability measurements and what they really mean. The crazy world we live in today depends on so many things runnig, its also so hard to measure your uptime, The uptime metrics can mean a lot of different things. The site is up and accepting traffic, but can users make changes or submit orders, there is a lot more to it than just up or down. I really appreciate Brittany’s story from Nike nested in there.
The SuperMini nrf52840 is a sick controller for building keyboards, affordable, easy to get, and compact. Bluetooth and wired setup just works in zmk. This page has a nice image of the pinout.
interesting UI for RAG based workflows, i.e. chatting with your documents. It looks like it can run a number of models, feels like ollama with RAG and a nice web ui.
Bluesky is almost excatly like twitter was when I joined years ago. It’s gone crazy lately bogged deep in politics, bots, and ads. I’ve seen like two scroll pages of ads in a row, its nuts. What I did not know before Joel pointed out here is that the feed I am looking at is my following feed, its only feed of people I follow in descending order. On bluesky you get to pick your feed!!! This feels like tweetdeck did back when we were able to run that. You could tune in search terms and save them it was glorious. Bluesky has some really interesting ones that you can use like popular with friends, only posts, my bangers, that have a pre defined algorithms.
This man is responsible for making gaming on linux what it is today. Such a heartfelt story to hear that reviving his dad’s machine was at the core of what drove him to do what he has done for the wider gaming on linux community. Update on your schedule, remove all the tracking and bloatware, this is what drove him to start using linux before making it accessible for his Dad.
But really do update, this is not your 2002 PHP box, things need updated and regular updates help the process.
Today I learned that the docs in postiz are a bit behind, (fantastic docs btw, they are to the point, and cover almost all of what you need). The docs state that you need to include an R2 bucket to handle uploads.
This issue shows that more work has been done, one of which is local storage. The compose file they use in the quick start has the required env variables to set this up.
STORAGE_PROVIDER: "local" UPLOAD_DIRECTORY: "/uploads" NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"
looking into my running instance I can see my images there.
Just tried using my twitter api key for the first time in quite awhile. Apps now need to be tied to projects in order to work. It looks like projects are where pricing comes into play. Thankfully they still give a free tier for doing small time things for myself. You can really see the effect that llms have on these things though as it is 5x more expensive to read posts than to make posts currently. Data is the new gold for these kind of companies.
Wild that the podman-compose github readme calls out k3s as an alternative.
compose definitely has its place, especially for local development on a developers machine, its so much easier to stand up and get things like hot reload up and running smooth.
The work on podman-compose by containers.
a script to run docker-compose.yml using podman
Intereresting someone built a blog generator in bash. it comes with normal markdown to html, static content, robots.txt, sitemap, rss, and tags. It uses pandoc to take markdown to html and mustache for page templates.
Css is getting so good, new things like interpolate-size are making things that use to require some deep expertise and hacks intuitive and easy.
Looks like a great start to a rules file for fastapi.
I have never heard anyone say this. It feels weird to me. The other early return, find and handle errors early all make sense to me, but happy path last is new to me.
Really interesting way to generate a rules file for agentic workflows based on your current repo. John uses gitingest here, looks like a fantastic tool, but probably not useful for most private repos. I’m sure you can replicate the same thing in a private repo wtih a small amount of effort the few times you need to do it. gitingest looks like a great way to pull in some extra context for some open source dependencies that you have though.
Gitingest has a python package on pypi that you can run with uvx, and it accepts the same arguments as the web version, right in your terminal
Looking for inspiration? gitingest by coderamp-labs.
Replace ‘hub’ with ‘ingest’ in any github url to get a prompt-friendly extract of a codebase
Replace hub with ingest in any github and get a prompt friendly codebase ready to feed into any llm. It combines the entire codebase, based on a gitignore style glob that you pass in, into a single TXT file.