@movq At work, I mostly open Jira tickets in new tabs and don't navigate them. But yeah, GitHub unsurprisingly fucked up here. One more reason not to use it. ;-)
git show -s --pretty=format:%cI
Btw. the versions in the search.twtxt.net and twtxt.net footers are both a bit wonky now. 8-)
Btw. how many accounts are there currently on twtxt.net? https://twtxt.net/user/stats/twtxt.txt looks like a grave, too. :-D
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.
[](https://lyse.isobeef.org/abendhimmel-2024-05-03/02.jpg)
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.
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! ;-)*
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.
make dev works perfectly.
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. ;-)
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.
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.
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!
Amazing sceneryhttps://lyse.isobeef.org/wanderung-2024-04-28/
Ears showing in the grasshttps://lyse.isobeef.org/waldspaziergang-2024-04-29/
-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. ;-)
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_
> IBM has realized it's cheaper to buy Hashicorp than to buy Vault licenses
@bender Holy cow, congrats on that title. I do have plugged in the more important equipment in a power strip with surge protection. The weird thing was, that only one of the monitors went black for a second. The other one (both are behind surge protection) remained operational the entire time. Maybe EMP? It was closer to the window than the other one.
@bender Fenster 11 → Windows 11; KraftPunkt (or Steckdose) → PowerPoint; Deppendrehkreuz (awesome translation btw, I had to laugh hard!) → GitHub.
I came across several different birds and two deer. 36-38 shows the same one, one meadow further, another deer jumped across the road. That was cool.
The focus often wanted to do its own thing, unfortunately. 25 shows the flatness of the Kaiserbergsteige (literally "Emperor Mountain Steep Road").
Flower snowmanhttps://lyse.isobeef.org/waldspaziergang-2024-04-21/
Yeah, HDDs aren't the fastest things in the world. :-)
Yeah, stopping the scanning thread is more a learning experience than a necessity. The scanning message is hardly visible in your videos. It's already very quick.
Always great to see that bugs are quickly fixed.
There's a tiny typo in the second to last paragraph: "Windows NT is something that I _had_ no contact with…"
Content-Type: text/plain; charset=utf-8 did the trick. Something in the twtxt client must have incorrectly guessed ISO-8859-1 or something along those lines when there was no charset advertised in the response header.
ncdu shows it at the bottom. ;-) But it's actually pretty smart, to be honest. More space for precious content. And the title bar exists anyway, so why not make use of it with something helpful? Also, with entries being in descending order, it's actually natural to show the sum as the even higher number above the largest entry and not at the bottom in another status line widget. 8-)
What the heck is going on with the encoding here?! The feed's
Content-Type header does not include any charset, but I'm still relying on the official twtxt client to fetch and parse feeds. Haven't noticed this with any other feeds. Where in the chain is this messed up? :-? Seems like the "space" is the Unicode line separator U+2028, that we use for newlines.
Maybe WTF-8 encoding!?
View from the edge of the forest into the lovely lit distancehttps://lyse.isobeef.org/waldspaziergang-2024-04-18/
Ah, interesting. Ui, that can hold some water. Certainly looks like a water level gauge to me. Maybe a precaution for a hundred-year flood or something like that. Or is there a dam nearby? Could be a facility to reduce damage in case it breaks.
At one point I thought I better grab my camera out of my backpack, so whenever something comes up, I'm ready. But I was too lazy and thought, well, I just wait until there is a nice subject and keep going instead. No joke, ten meters further I came across two squirrels. A red and a brown one, sitting on a tree at just one and three meters height two meters away from me. If I only had unpacked my bloody cam a few seconds ago! I just watched them sit on the tree and then tried to slowly strip my backpack and grad the cam. It was still booting up when they decided it was enough sitting around and climbed higher. What a silly move on my end, damn.
I tried to improvise some Lyse Street View, but felt really uncomfortable to photograph other people's houses. Somehow my cam produced sooo many blurred shots on the way up still away from the village, it's unbelievable. I scrapped nearly the entire project. Only very few survived. There were heaps of people on the mountain summit, so I quickly left again.
Flower bed in the villagehttps://lyse.isobeef.org/waldspaziergang-2024-04-14/
Looking forward to next week's rain and temperature drop to 16°C or even 8°C.
Yeah, walking next to a highway is torture. I try to avoid it as much as possible.
Nice! The third photo looks like a Kneipp basin. What's that round tunnel? I love those moss-covered rocks, they just look so beautiful.
That's really impressive I have to say.
Was that a highway that you were walking next to? The last one shows a really cool scenery. I dig that.
-ldflags '-w' still 1.3 MiB. Growing with each Go release.
The mountain is 684 meters above sea level, so this makes for a difference of about 350 meters in 5 kilometers (most direct trip). Plus a little bit up and down here and there, or more, depending on the selected route. But it's not climbing stairs, so it's much more pleasant I'd say. Kudos to you! The last section is the actually steep part. Each brown contour line marks an increase of 10 meters. Sure enough, I'm glad when I finally reach the summit and can pause for a breath. :-)