the myth of nixpkgs contribution me: i consent maintainer: i consent nixpkgs merge bot: i don't isn't there somebody you forgot to ask

what the heck is *S-1-5-80-0,*S-1-5-99-0 and why am i reverse engineering some win32 .sys stuff in order to work on uh i don't know, haskell maybe?

i should make a meme that puts YOU CRASHED red letters on top of my windows vm install screen but i'm a bit exhausted

the litellm supply chain attack is a result of exposing ci secrets on the wrong granularity. any logic that uses secrets should live in an isolated downstream job, and github actions allowing people to be lazy and scope secrets to step instead of job levels is a footgun that will continue to fire

i've been rage sniped by the ghc project to do devops work

paradox of open source: - do more work - more work * same error rate = more errors - more errors * other maintainers = more frustration therefore, work harder = more frustration, q.e.d.

why is lunduke so mad at rust. i mean rust is pretty diversified right, there's bro rust and there's woke rust

is it being autistic or is it a sign of burnout by staring at build logs, straces etc and doing nothing

kernel hopping is not what i expected when managing my own server. why do i need to read lwn just to keep the thing alive

bcachefs is worth a try on my next box. btrfs-like subvolumes but even faster (what arch wiki says), and a great fit for ssd/hdd mixed setup. a slight pity is podman falls back to fuse-overlayfs but i can live with that

every language has nice sales pitch until you open their issue tracker, sort by severity and then start screaming and can't sleep at night

kernel not cached in nixos hydra is a bad omen from the universe and i should have stopped the upgrade before a server reboot

must resist temptation to puncture a swollen battery

mini hackathon workflow: - baseline build of upstream master - spawn new containers from btrfs snapshots of the baseline build - same prompt, different agents, yolo mode zero handholding - forget about agents, organic work, monster overdose this gamifies the work quite a bit and i like it

my server is up but my laptop is down, the vibe coded 6.18 wsl2 kernel and btrfs hypervisor brought windows to its knees

laptop fan spins up when remote builds are hot. and it turns out that vscode terminal is really the culprit especially if you have 8 panels each rolling hadrian build logs

the hardest challenge of writing a coding agent is not getting banned by impersonating other agents

qwen 3.5 9b runs comfortably on my laptop with around 60 toks/s and it's undoubtedly the best in its size class (as of today), useful for tasks like local retrieval that doesn't require broad world knowledge

gemini 3.1 pro increases censorship on magic, occult and mythology. i mean, pretty much the only reason i use gemini is for creative writing, which is a use case the openai models completely gave up. time to bleed my wallet for openrouter then

is "no bullet points" the same thing as "don't think of an elephant"

great, my server is down again as i'm about to go for a trip

with-style apis are a huge pita to deal with in 2026. you can use codensity over io to make composition less painful, but it still doesn't support interleaved resource lifetime and it grows the stack when it doesn't need to. resource safe my ass, stop hiding the sharp edges, nanny maintainers

nice, servant has added official support for generics. would be better if official tutorial uses generics but baby steps

also, m&s sells better food than auchan

local uncensored models are not just for erotica, but also for preventing one from slowly internalizing the censorship built into proprietary models without even realizing it. similar to how agenda is curated in news and social media, the same happens in ai, and a freer mind needs to jump extra hops

today's visit to baker street 221b has been a mild disappoint. i bought a deerstalker hat, the rooms have good vibes, the staff in victorian age maid costume explained things well. then i pointed at a socket in the wall and asked "is that also from victorian age" and maid rolled her eyes with "heh"

off context question. does the society runs on people being afraid of consequences or people being nice

one of the (increasingly rare) moments where ai wrote crappier haskell than i do is using `ScrubbedBytes` for secret. the model doesn't realize that 1. it's from an abandoned package 2. the original idea is still fragile 3. it should use libsodium managed memory in the first place

lmao starbucks and costa wifi in london actively blocks dns over https providers to harvest my data

parents: ai is all over the headline! you must keep up with the trend and otherwise you'll end up in the streets! me: actually i do daily drive it (talks about first hand experience and project ideas for 10min nonstop) parents: good job son, how much extra money are you earning per month? me: .....

i dislike going through a disaster recovery playbook (aka stolen phone) before a travel. especially the fact that the playbook is written after it happened once here in paris, and maybe i should feel lucky the playbook has not been actually used since then

the hashline edit method for llms is really thought provoking: x.com/_can1357/sta...

only making notes via markdown and bullet points might have shut down some parts of my brain that i'm not even aware of. i used a remarkable once but couldn't remember why i gave it up; this time i need to try using a dead tree notebook and a ballpen

take the state out of the agent

tired: do free tech support in my own spare time inspired: vibe code other people and say natural language and shit gets sorted out in real time

captcha that works for a terminally online broken soul: hello, here is a list of tweets, please classify whether each tweet is posted by wint or gpt. reach at least 2/3 accuracy to proceed

be horny, be schizo, be human

simon pj once said code comment is like a letter to your future self. it's a very good insight, and i can't wait to put this into every module i touch: ```haskell --- if you're still working on this, go touch grass, make better use of your life ```

i've never managed to get to the end game stage of satisfactory. but i had enough fun already, and the soundtracks are still the best late night focusing background music for me

i'm not supposed to know what is /dev/dri/renderD128 or systemd SupplementaryGroups or how nixos manage mesa and vulkan. but on the flip side, i finally managed to offload some layers to the integrated gpu

ah you can signal(SIGCHLD, SIG_IGN) in pid1 and the kernel would ensure there would be no zombies, and this works even in a pid namespace...

i can run nixos in podman now. feels nicer than nixos container since it uses rootless podman instead of rootful nspawn, has properly isolated nix store in its own rootfs, and is portable across host distros that support podman

if your build artifacts are sensitive to absolute path you're committing a crime

good instruction following still means less censorship, same vice versa. and that's exactly the reason mistral models are still quite useful today despite not in top tier

Here's my AI Skill Threat work which I now think was very prescient and a little ahead of its time: osf.io/preprints/ps... Here's an introduction to psychological affordances for developer experience folks: osf.io/preprints/ps...

hobo sapiens

i vibe coded a nixpkgs overlay to enable krun backend for crun and now i can start paravirtualized podman containers that are run by kvm and have their isolated kernel instances, nice! sadly i don't think putting up a nixpkgs patch is suitable (long review time plus "meh fuck ai" vibe in that space)

you can add `services.snowflake-proxy.enable = true;` to your nixos config to donate bandwidth to the tor network and help defeat censorship without publishing your ip to the publicly available tor relay list

nixos managed github runner has a bunch of ridiculous systemd hardening options without an escape hatch. my previous runner copy pastes and undo those options, but i just discovered `podman --remote` today so things work as long as ProtectHome is set to false and the podman user socket is accessible