@aelaraji@aelaraji.com Perfect! :-D

@movq@www.uninformativ.de it’s a shame we have to ruin such great technology that only depends a lot of this with crappy bullshit nonsense like advertising we’ve been into responses 🤦‍♂️

@prologic@twtxt.net This was to be expected and I’m glad that it’s finally happening. I seriously hope that AI/LLM output gets swamped with advertisements or unwanted code, so people see what they have gotten themselves into, especially the “vibe coders”.

@david@daiwei.me You might have ended up loading the page in an unfortunate moment while I was reworking it. 😅 The CHANGES file is there, in the browser:

Advertise in ChatGPT | Hacker News Seriously?! 😳 wut da actual fuq?! 😱

@aelaraji@aelaraji.com Perfect! 👌

@prologic@twtxt.net Sorry I haven’t seen your question before! and to answer your question, no, it wasn’t hard at all. it’s a simple go build …etc. as instructed + scp twtd to remote + made a systemd service for it to (re)start automatically under a dedicated twtd user for lols. + poked at the Caddyfile to reverse-proxy a couple of paths and called it a day.

Too much info?

@david@daiwei.me @lyse@lyse.isobeef.org How about Augmented Ignorance ? it packs a better punch, doesn’t it? 😅

@movq@www.uninformativ.de Yes good I think we are too! 👌

@david@daiwei.me Go down to “Releases”, there’s a link to the CHANGES: https://movq.de/git/jenny/CHANGES.html

@lyse@lyse.isobeef.org Yeah, the feed names are legacy and I didn’t want to set up redirect rules. (I can’t really tell if anybody actually uses them …)

Extracting the info from the CHANGES file would be nice. Maybe I’ll add that. :-)

@aelaraji@aelaraji.com @david@daiwei.me Hahaha, neither did I came across this before. :-D

@movq@www.uninformativ.de Similar to my Go IDE at work. GoLand hangs so often in this giant code base. :-D (But it could also be one or the other snake oil that’s forcefully installed and fucks with me every day.)

@david@daiwei.me Hahaha! The thing is, it doesn’t taste as good in summer as in winter for some unknown reason. Two or three decades ago I asked my grandma to bake some of her amazing gingerbread in summer. But she always refused, claiming that this only really works in winter. Of course, I didn’t believe that. Finally, after years of begging and pleading, she finally made a tray. And to my surprise, she was right. It wasn’t bad, no, no, not at all. It was really yummy. But the gingerbread in winter was just better. :-/

Maybe I should give it a shot myself. Perhaps she slightly changed the recipe on purpose. So that I will never break the tradition of seasonal food again. :-P It worked, at least I never asked her to bake gingerbread in summer again. :-D

Pretty cool, @thecanine@twtxt.net!

@movq@www.uninformativ.de Good question. Tarballs are probably not needed, but might be convenient for people who don’t want to or can use a version control system. Not sure if there are non-techies who use your software. Tarballs for branches are overkill, though, I agree.

Looking at this more closely: As for the feeds, how about filenames “tags.atom” and “commits.atom”? Unless, of course, they were already named like that before.

For the tags feed it would be cool to include the actual changelog entries to be more useful if somebody takes this approach to get notified of new versions. But that would mean you have to duplicate the changelog entry into the annotated tag. And then you can’t fix changelog typos in the feed anymore. Alternatively, the feed generation would need to extract the section from the the CHANGES file. That has the benefit of automatically providing changelogs for past versions in the feed.

I finally built a prototype of a marking gauge with a cutter wheel out of some scraps.

https://lyse.isobeef.org/tmp/streichmassprototyp-mit-messerrad/

It had been a long time in coming, I bought some replacement cutting wheels three years ago for exactly that purpose. I also found out that I need more M3 countersink bolts for future marking gauges that I want to make (maybe two or three more). Luckily, I had exactly one. I thought I got way more than that, but M3 is very, very scarce in my collection. My M3 bolt was barely long enough to attach the cutting wheel to the bar. But it’s okay for the prototype.

I was pleasantly surprised that I managed to drill the 2.5mm diameter hole almost perfectly in center in the 8mm diameter aluminium round bar. Center finder, drill press and vise with a vertical prism for the win!

I knew upfront that the M5 steel bolt to lock the bar in place definitely needs to be replaced with a brass or aluminium one (maybe with a knurled head). Otherwise, it cuts into the aluminium bar and leaves ugly marks. These burrs might even scratch the workpiece. But, of course, I don’t have any brass on hand either. Alternatively, I swap out the aluminium bar for a steel or even stainless steel one. Stainless might be tricky to precisely drill and tap, though.

I already learned a few things by making this prototype. The final wooden fence can be even a bit bigger. This round thing behind is also too short, I’d like it to be a tad longer and thicker. The final one will be made from hardwood, not spruce. Other than that, it’s great and already more practical than my store-bought marking gauge with its round fence. This only causes the tool to roll around on the workbench. Or even roll off. Stupid design.