@davidgerard that post is a *goldmine*
New blog post: Lanzarote
https://jmtd.net/log/lanzarote/
A stream-of-conciousness blog post to get back into the habit, discussing our holiday to Lanzarote, Autistic Burnout, the UK special needs education system, Pandoc parsers, the AI control problem and the issue of copyright and LLMs. #software #debian
https://jmtd.net/log/lanzarote/
A stream-of-conciousness blog post to get back into the habit, discussing our holiday to Lanzarote, Autistic Burnout, the UK special needs education system, Pandoc parsers, the AI control problem and the issue of copyright and LLMs. #software #debian
New blog post: FOSDEM 2026 talk recording available
https://jmtd.net/log/fosdem/2026/video/
The video recording and slides for my FOSDEM 2026 talk (Java Memory Management in Containers) are available. I hope to write a proper postmortem blog post soon. #containers #java
https://jmtd.net/log/fosdem/2026/video/
The video recording and slides for my FOSDEM 2026 talk (Java Memory Management in Containers) are available. I hope to write a proper postmortem blog post soon. #containers #java
@rivets I thought I did too ;) At some point I want to look at making blog posts first-class Fediverse objects
https://jmtd.net/log/lanzarote A stream-of-conciousness blog post to get back into the habit, discussing our holiday to Lanzarote, Autistic Burnout, the UK special needs education system, Pandoc parsers, the AI control problem and the issue of copyright and LLMs.
@textfiles thank you for your service 🫡
My primary reason for working on a moinmoin reader for pandoc has gone away (change of strategy for migrating Debian’s wiki) but I’ve kept working on it anyway.
@textfiles hi, random Q, I think you have a one-page site with a fanfare ending “internet!!!!” But I can’t remember what it is. Can you tell me please?
@pndc yes. To be clear that was an extrapolation of my argument to not fix known issues; I don’t feel it should be done!
@pndc I wouldn’t describe a vulnerability as a back door unless it was not well known or deliberately obscured. I do feel the plain text nature of telnetd is a fault, yes, but I appreciate others may not. There are other decision decisions I also feel are faults (e.g. accepting the client’s ENV). Also, it’s de-facto unmaintained.
Reasons `less` is a reasonable default man pager: scrolling up and down, and quitting, are reasonably intuitive and discoverable for beginners. Beginners benefit the most from being able to read man pages.
I’d love it if the default could also handle jumping to (and back from) a cross-referenced manual. (Neo)vim does this, but IMHO would be a bad default for other reasons.
I’d love it if the default could also handle jumping to (and back from) a cross-referenced manual. (Neo)vim does this, but IMHO would be a bad default for other reasons.
Does fixing security faults in telnetd simply encourage people to use it? IOW, would deliberately _not_ fixing them be a better strategy? I suppose that argument could extend to: would it be good to _introduce_ security bugs to telnet, overtly?
@werdahias I’ll have to take a look. At the moment I use nvim which is better than a simple pager but I feel needs more
Julia’s excellent vlog about man pages (https://social.jvns.ca/@b0rk/116093529820975727) reminded me I was thinking about Debian’s policy of “every tool should have a man page”, and how often that isn’t true.
I’d like to see the default man viewer have some more quality of life features, especially for newer folks
I’d like to see the default man viewer have some more quality of life features, especially for newer folks
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
Now, the moment you look at a repo, you can immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
@vaurora eating lunch at a resort hotel with my youngest daughter. About half way through a week vacation. Unclear if it was a good idea taking my eldest, who is in autistic burnout. Some good moments, some bad.
No Boilerplate