vim-classic in #OpenBSD
https://marc.info/?l=openbsd-ports-cvs&m=177461514809884&w=2
Posting mostly about tech stuff I'm working on but happy to read and chat about non-tech stuff too. I'm grateful to be learning so much about the world from all of you.
Tech stuff I'm working on currently includes OpenBSD, Apache Subversion, Software Heritage, Game of Trees, @gothub, and Dulwich.
Toots get auto-deleted after one month.
| www | https://stsp.name |
| languages | de/en, a little fr |
| cities | Berlin / Brussels |
| pronouns | he/him/his |
vim-classic in #OpenBSD
https://marc.info/?l=openbsd-ports-cvs&m=177461514809884&w=2
@vanhoefm I am leaning towards only supporting the fixed variant of #WPA3 in #OpenBSD.
Hash-to-element has the advantage that ifconfig can compute the PT in userland, leaving the kernel to compute only the PWE during association.
Not supporting the workarounds for the broken version of WPA3 might help push people to updating (or replacing) their APs in case they are broken (or unfixable), at least in the OpenBSD user community. I don't think that would be a bad thing.
As far as I understand, hash-to-element can be added to older WPA3 devices with a software update. It doesn't require hardware modifications. Correct? If so, all vendors should be able to provide an update which adds support for hash-to-element.
Backup all the things with #plakar and #OpenBSD !
https://x61.sh/log/2026/03/25032026151800-plakar.html

I presented at the local planetary journal club this morning about the 3 articles I co-authored for The Conversation in the past weeks about the effects that one million satellites would have on the night sky, the atmosphere, and the orbital environment (spoiler alert: all very very bad)
And one on light pollution that I thought would get published today but might not be out until after the weekend.
Doing a small bit of work on #IPSec for a change.
nom nom nom 🍪
It has taken me a while to put into words why I dislike the use of AI in open source. I think I finally pin'd it down.
One of the best aspects of open source has always been sharing in the excitement around a project. An author spent time and energy to make this project that they were excited about, or solved a problem they had. You had the same problem or were inspired by their excitement and joined in on the fun.
Now people are shitting out entire code bases to do something and I just can't get excited about it. If you can't be ars'd to put in the effort, neither can I.
Then there are the other aspects: paying a company to be a Developer™, now there is an expectation of HyperProductivity®, environmental, ethical... the list goes on.
What happens to your codebase if you stop paying? Are you going to maintain the 200k lines it shat out in a week? Doubt it. Your skill set has been captured. Your project has been captured. Now you must pay to access it.
Fuck that.
What's if you could ~$ git clone SWHID?
"You’d end up with git clone as a content-addressed fetch primitive rather than just a URL fetch, which is an interesting building block for reproducible builds and supply chain verification."
A nice write-up by @andrewnez on git remote helpers 👉 https://nesbitt.io/2026/03/18/git-remote-helpers.html