All packed, ready to go.

@mckinley@mckinley.cc That’s a cool idea!

@prologic@twtxt.net Kehrwoche! :-)

@prologic@twtxt.net I noted it in my calendar, looking forward to it. :-)

@prologic@twtxt.net Cool!

@movq@www.uninformativ.de I’m subscribed to 48 feeds at the moment. And only a fraction is actually active.

@prologic@twtxt.net Oh, was I? I don’t recall any of that. But who knows. ;-)

@prologic@twtxt.net I won’t see any activity again, unless somebody else I follow interacts with them. Yep, fetching the feeds still happens with a patched version of the original twtxt client. tt is just a viewer of the database contents.

Righto, it’s time for a rotation into archive feeds again.

I just cleared my following list. Kicked out all the 26 feeds that have not been updated for two years or more. This will reduce a bit of useless traffic.

@prologic@twtxt.net I figured, yep.

@prologic@twtxt.net Does one need a build timestamp anyway? That’s an enemy to reproducible builds. Maybe just use the commit timestamp? That would work at least for official releases. It would be off for dirty working directories during development, though: git show -s --pretty=format:%cI

@movq@www.uninformativ.de Yeah, I did.

@prologic@twtxt.net Oh wow, still so many left. Cool.

@prologic@twtxt.net Looks much better, although I’d strip the “v” prefix in yarns’ “v$branch@$hash”.

@prologic@twtxt.net Nice!

Btw. the versions in the search.twtxt.net and twtxt.net footers are both a bit wonky now. 8-)

@prologic@twtxt.net FWIW, at least five feeds were not empty. But their feeds still looked dead, since the last posts were from 2020 and 2021. So that was probably before the date of last login was recorded.

Btw. how many accounts are there currently on twtxt.net? https://twtxt.net/user/stats/twtxt.txt looks like a grave, too. :-D

@movq@www.uninformativ.de wc -l .zsh_history gives me 7100. That’s surprisingly a bit more than I thought. I used to regularly clear new stuff by hand and keep important commands to about twenty-something. I don’t recall the numbers anymore.

@bender@twtxt.net In the end the cameraperson overtakes him again. But yeah, who knows with today’s AI crap everywhere.

@movq@www.uninformativ.de @prologic@twtxt.net :-)

@movq@www.uninformativ.de Yep, I use it all the time, too. Except for Go, where I use Ctrl+x+o for Go-specific completion. But Ctrl+n still comes in very handy for strings and the like. In fact, it scans all the open buffers for completion suggestions.

Quite the acrobatic piece: https://youtu.be/p5GU_BvvHso

We had a nice sunset: https://lyse.isobeef.org/abendhimmel-2024-05-03/

@bender@twtxt.net Rest assured, it was really disgusting.

Wow, it’s crazy how many people already delivered donations for our scout flea market today. Collecting and delivering officially starts tomorrow, today was just the setup. Covering the floor of the town’s multipurpose hall, transporting and arranging beer tables and benches, setting up sign, that sort of thing.

But on the flipside, we’ve also been abused as dumpsters again. Some asshole brought us a deep fryer. With the oil still in it. Unfortunately, we discovered that too late.

The big work starts tomorrow morning at 8:30. And the flea market where we actually sell the stuff is on Sunday. It’s gonna be a hell of a weekend.

@mckinley@twtxt.net When typesetting our graduation newspaper (“Abizeitung” as we call it), I destroyed the work of a whole day. :-D

I plugged in the USB stick of my mate (exact same model as mine) to do a backup of that day’s work. Since mine was already plugged in, the mount path /media/USB_DISK or whatever it was already existed. Throughout the day I saved everything on my drive (I don’t know the reason for that anymore). The newly plugged in thumb drive then got automatically mounted by Konqueror as /media/USB_DISK2 or something like that. I wanted to show off my other mate how cool Linux was and how quickly the command line was able to get things done. By force of habit I cded into the wrong path to first rm -rf *, so that there was room for the new stuff. Indeed, the data was ruined super quickly.

When I noticed my fuckup I aborted immediately, but it was already too late. I went to the family computer to research recovery tools. All the files I was able to restore were corrupted. The Scribus XML files ended somewhere in the middle. So then we decided to redo all the work instead of wasting more time trying to fill in the missing XML. Unsurprisingly, it turned out that not only the last closing tags were missing, much more of the contents disappeared. I remember that I gladly noticed the second typesetting round went much faster. :-)

I could be totally wrong here, but I think one problem was that write operations to external devices were not immediately synced, one had to expicitly flush the write cache, e.g. by umounting it properly. Early on in the typesetting process we decided to have each page or spread as separate *.sla, because a) our computers were not powerful enough to handle a large project and b) once the layout template was cast in stone, we could easily work in parallel and join everything in the end. That helped to limit the damage to just my work. My mate’s was still there I believe.

Oh yeah, that’s certainly the best strategy, @bender@twtxt.net! ;-)

@movq@www.uninformativ.de Wasn’t too bad in the end. Just a hand full louder thunders and decent wind. It smells really good after the light rain. Mjam!

The thunderstom is closing in on us now. It just started to drizzle.

@prologic@twtxt.net I read the help and it’s a bit clearer now. Still a bit wonky. I will probably have it already forgotten by this evening. “Term” is exact match and “Match” adds some kind of unknown fuzziness on top.

The second bullet point can be addressed I reckon. It’s purely a UI thing. Also, I’d add a short explanation for the search types next to them, so people don’t have to look things up all the time through the help or even follow the links to the bleve documentation.

I like the magic detection™. That’s what people expect. At least I did.

Thanks, @prologic@twtxt.net. It was taken near the dairy farm. Came down the hill in the forest on the right and tried my luck. It turned out the photo gods were in my favor. :-)

@bender@twtxt.net I see, thanks for educating me. :-) At least you’re interacting with native speakers a hell lot more than I do. I’m speaking English almost every day at work, but it’s basically never anybody’s mother tongue.

@mckinley@twtxt.net For testing purposes make dev works perfectly.

Thank you very much, @bender@twtxt.net! I just linked the thumbnail to safe on people’s bandwidths. I figured if someone wants to view the photos, they just go to the album anyways. If one has no interest, it’s less invasive on them.

Picking the money shot is always tricky. Especially since I have been sorting through them for an hour or more. I try to keep at most 10%. And yes, I very often do hate myself for pressing the trigger so many times when I come home. So by then I’m kind of sick looking at them any more. :-D Sorry, I try harder next time. ;-)

@bender@twtxt.net Damn, I got caught. :-D

Btw. how does it work in English? In German it’s ambiguous which weekend one addresses when saying “next weekend”. Is it the coming one this week or the one in the next week? Different people interpret it differently if it is not inherently obvious from the context, like when talking about dates. I also noticed that sometimes the same person even switches between meanings. I think I do, too. But I don’t know why.

Maybe it depends on when one says it. I could be totally wrong here, but earlier in the week, like on Mondays and Tuesdays chances for “weekend in the same week” are higher than towards the weekend (Thursdays and Fridays), then it’s more likely to refer to the weekend in the next week. And yes, the week of course starts on Monday. ;-)

Not sure if it changes with dialects. :-? I assume that doesn’t play a big role and is the same for all German-speaking regions.

On the other hand, “this weekend” is very well defined as the upcoming weekend in this week. It’s only the term “next weekend” that can be problematic.

@prologic@twtxt.net Good question. Two things come straigt to mind, although, I’m not sure how low hanging they are. Probably not even remotely.

1. I don’t know what these three search types mean: “Match”, “Term” and “Query String”. I could read the help page (I probably should), but they are sooo far off from my little brain that I can’t even think of a possible explanation. My (possibly broken) intuition would categorize “Match” and “Term” to be the same. Zero idea what “Query String” is supposed to be. But then I think a search should be so easy to use to not having to read up on it in a manual. Admittedly, the basic search works alright.

2. When “Match” is the default, why is it not selected? Similarly, when it searches all fields by default, why is “_all” not selected? This technical spelling “_all” with the leading underscore also doesn’t look pleasing to my eyes. It’s been a hell lot of time that I looked at the code base, so I forgot everthing by now, but that should be easy to fix.

3. Okay, three things. :-D Apart from the search results taking up soo much space, it would really be nice if the markdown would be rendered. Yes, this is probably very tricky, as the matching search terms are highlighted. So I imagine both the highlighting and markdown rendering probably contradict each other. Also, how to go about matches that are part of markdown link URLs, image alternative texts and the like. Not easy at all.

I reckon that’s certainly not what you had in mind or wanted to hear. :-( Sorry about that. I doubt it myself if this is any helpful feedback.

No promises, but I try to toy around with the search more in the future. Maybe even look into the code base and see what I can do. The next weeks will be full of activities with the scouts, though. So don’t expect something in the near future.

@prologic@twtxt.net Thanks mate, looking forward to the next weekend. :-) It appears I’m just in time with this tiny usability improvement: https://git.mills.io/yarnsocial/search/pulls/22

@movq@www.uninformativ.de I hear you. :-( Flight tickets are way too cheap. I’m also astonished, that night flying restrictions don’t apply for politicians. Of course.

@prologic@twtxt.net I believe that only a search box on the front page is better. Just like it is now. I still haven’t got used to the advanced options, but that’s an entirely different story.

@bender@twtxt.net Glad you do. :-D

@prologic@twtxt.net @movq@www.uninformativ.de Thank you! :-)

@bender@twtxt.net Let’s hope your life quality will improve with that single purpose tool. :-D

@prologic@twtxt.net Heck yeah, grats!

@prologic@twtxt.net Like @movq@www.uninformativ.de said, it is a very niche thing. But that has always been a good thing in my opinion. And I do still think so. :-)

yarnd in particular is too heavy for me personally, I just like the simplicity of wacking a file on my server and voilà. But other than that, I still support that software. :-)

And I come back to twtxt.net every now and then to read up on conversations that seem to be incomplete in my own client. Like if a new feed appears that I don’t follow (yet). That’s certainly a convenience that I do enjoy. Thank you for that!

Went on a 20-25km long hike yesterday. Birds were beautifully singing, the lovely smell of freshly cut grass was in the air and the terror of rotary mowers reached my ear constantly. It was a bit cloudy, but the sun peaked through every now and then. Really a wonderful day to be outside. About 21°C and some wind.

Amazing scenery

https://lyse.isobeef.org/wanderung-2024-04-28/

@adi@twtxt.net Oh wow, I’m really surprised that it still sounds a lot like Stairway To Heaven. I’m pretty sure I would have gotten that even if I hadn’t read the title. Music-wise of course. Not from the lyrics. :-)

Damn it! My camera battery didn’t charge, so all the nice deer and tad pole in a puddle imagery did not work out. :-( I saw two pairs of ears showing in the grass. Suddenly, three deer took off. One went straight into the strip of trees nearby and back behind me into the woods. The other two ran more into the meadow and then alongside the path I was taking. They unexpectedly overtook me and crossed in front of me to the other pasture. Then they headed back into the forest like rockets. Holy cow, they were super fast. Really amazing to watch. Battery flattended after the second of video I recorded in the beginning.

Ears showing in the grass

https://lyse.isobeef.org/waldspaziergang-2024-04-29/

@bender@twtxt.net @prologic@twtxt.net Thanks mates. I’m not the only one, @xuu does, too. :-)

Executing all tests of the online registrations I’m building for the scouts takes now 70 seconds. Initializing a new SQLite database in RAM and creating all the tables for each test case sums up and takes its time. During development cycles I more often resort to the -run flag for go test to specify only one area of tests to be executed. Much more fun this way to quickly go back to writing code.

At least the service layer line coverage is a whopping 99.5%, branch coverage is 93.3% (the latter could still be bumped slightly). However, only 17.6% lines of the web layer are covered (I definitely should increase this by a lot). This still good test base, if I say so myself, came in extremely handy a lot of times when refactoring stuff. Esp. the service layer changed, web not so much. It slows development down quite a lot, that’s for sure. I reckon it’s easily five to ten times more effort to come up with useful tests than writing productive code, probably even more. I’m bad at guessing. But the confidence of not breaking stuff is sooo much more valuable. The tests certainly paid off in the past, zero doubt about that.

It takes a lot of discipline to first write all the tests in the service layer before doing the web stuff and finally see it in action and play around. It’s funny that I always have to force myself to do so, but in the end, I’m always happy to have done it exactly like that. It once again worked out very smoothely that way. But something inside me wants to fast forward. I wonder if that irrational part eventually fades away.

Having a code coverage report does make a night a day difference. It actually turns writing tests into a fun game for me. The older I get, the more I do enjoy writing tests. Rest assured, producing productive code is still cooler. :-)

I’m also sooo happy about vim-go. I can’t believe how much that sped up and boosted my development process.

Whoops, 57 minutes later, this message turned out much more elaborated that I initially envisioned. Oh well. ;-)

I just found out about last(1) and lastb(1) while wondering about /var/log/wtmp. This can come in handy! The filenames remain a bit mysterious: https://unix.stackexchange.com/questions/127211/why-are-utmp-wtmp-and-btmp-called-as-they-are

@movq@www.uninformativ.de Oh wow! Better not mess up with that responsibility. :-)