@kat@yarn.girlonthemoon.xyz True! :-D

@movq@www.uninformativ.de Yes, exactly that. It’s awful! And it’s getting worse from my perspective. Nobody in charge is ever gonna learn anything. I figure we just fully deserve this M$ crap, every single bit. :-(

Luckily, the most important development platform still worked for me, so I could actually do something, review code, pull and push, etc. But the calls with the screenshares were nightmares. Can’t see shit on such a tiny display with today’s extreme monitor sizes people use. Looking at logs, hahahahahahaaa…

@movq@www.uninformativ.de Neat, that sounds like a clever design with a table implementation. :-)

Oh, for sure! Complexity will definitely go through the roof and beyond with optimizations, no doubt. Maybe with the very simplest of the easy ones it might be still reasonably straight forward, but I also imagine that this has the potential to escalate very quickly. :-D

Another infrastructure apocalypse day at work. Linux and Windows users were unable to reach M$ services. No Outlook, no Teams, no intranet (Sharepoint), no Azure, etc. Mac users were lucky, though. Took whoever the whole day to resolve that. Shortly before I called it quits, it worked again. I haven’t read any e-mail today, used Teams mostly on the company phone, but it’s the plague.

And as I’ve forseen the other day, we have to deliver yet another workaround hotfix, once the other team eventually gets their stuff integrated that we should rely on. Good riddance it’s the weekend now!

@movq@www.uninformativ.de Oh, this is really awesome! :-) Hats off to you, that would take me forever to accomplish.

Haha, eleven bytes, how mean is that!? :-D But I already see you working on that as well at some point in the near future. :-)

@prologic@twtxt.net Totally fine with me, I don’t use it. I just have to when hacking on yarnd, because it phones this service.

@kat@yarn.girlonthemoon.xyz AKB48 and other spinoffs sound so great. I’m listening and whistling to them for hours now. I have no clue what the lyrics are about, but it’s just fantastic music. Thanks for introducing me to them. <3

@kat@yarn.girlonthemoon.xyz Wrrrrrmmmmm, wrrrrmmm, have fun! I think I played that about 15 years ago last time or so. I never was much of a gamer, always loved to code useless stuff instead. :-D

@kat@yarn.girlonthemoon.xyz Thanks!

@prologic@twtxt.net Those people don’t read tocs.

I’m refactoring (mangling four lines of of code with assignments into one function call) and man, do I love vim macros! Such a bloody amazing invention. Saves me heaps of manual labor.

Specifically those around 2:50min, 6:15min, 11:00min, 28:40min and 33:40min. :-)

@kat@yarn.girlonthemoon.xyz Cool, cool, congrats! I skipped around and noticed that you used some great background music. Do you have a list for me to look up? :-) Also, that’s a nice desktop wallpaper in the end.

@movq@www.uninformativ.de Woohoo! You selected a turing complete instruction set, so all good. ;-)

@suitechic@yarn.girlonthemoon.xyz It’s the exact opposite for me. :-)

@bender@twtxt.net I always schedule the next appointment right away. :-) Yeah, over here, it’s just winter. Nothing really surprising. But it gets us every time. I prefer the ice over the the fire for sure.

@movq@www.uninformativ.de That was the only time I left the house today.

Walking those few hundred meters to the dentist and home took me at least three times as long as usual. Complete sheets of ice on the footpaths, definitely ice skating territory. The dentist was caught in a traffic jam and arrived about an hour late. On my morning journey I saw two ambulance operations, one on the way there and the other one when I returned. Just 200m apart. I fear it’s going to be an exhausting day for all the rescue personell.

@xuu@txt.sour.is Haha, that’s cool! Be careful with reporting or they might sue you to death.

@arne@uplegger.eu Uuhhhh, more twtxt clients, very nice! :-)

@bender@twtxt.net Yeah, looks a bit broken:

@aelaraji@aelaraji.com @movq@www.uninformativ.de Damn, I forgot, too! And the clouds prevent me from catching up on that. But it’s really cool to hear that you were able to see something nice up there. :-)

@aelaraji@aelaraji.com Reminds me a bit of TeX which approaches pi by adding a digit with each bug fix in its version number. https://en.wikipedia.org/wiki/TeX#TeX82

@movq@www.uninformativ.de @prologic@twtxt.net Yeah, you won’t be disappointed. :-)

@prologic@twtxt.net This is fricking amazing, congratulations! :-) \o/

That’s a well done mapping of computer time scale to human time scale: https://youtu.be/PpaQrzoDW2I

Matt Godbolt is also a guy that I just enjoy listening to.

@movq@www.uninformativ.de Hmm yeah, you’re right. I should have checked for our location prior to getting too excited.

@aelaraji@aelaraji.com Yeah, a sore neck is always a win. :-P Here’s nothing really to see, all cloudy. And also a bit cold at -2°C. I don’t feel like standing still all that long outside at the moment. :-D

Heck yeah, that’s really cool! Let’s hope for a clear sky: “On the evening of 28 February 2025, all seven of the other planets in the Solar System will appear in the night sky at the same time, with Saturn, Mercury, Neptune, Venus, Uranus, Jupiter, and Mars all lining up in a neat row – a magnificent sky feast for the eyes known as a great planetary alignment.” https://www.sciencealert.com/a-rare-alignment-of-7-planets-is-about-to-take-place-in-the-sky

Your code apparently works just fine. Until it @doesnm@doesnm.p.psf.lt’t. ;-) The shell languages are weird and having some strange properties that one is just not used to when coming from other languages.

Well, I stand corrected, pre-wrap even! https://git.mills.io/yarnsocial/yarn/pulls/1186

PSA: Yarnd operators might want to define code { white-space: pre } in their CSS themes to render things as they’re supposed to look like.

@andros@twtxt.andros.dev I love how this is coming together! :-)

@kat@yarn.girlonthemoon.xyz To improve you shell programming skills, I highly recommend to check out shellcheck: https://github.com/koalaman/shellcheck It points out common errors and gives some suggestions on how to improve the code. Some details in shell scripting are very tricky to get right at first. Even after decades of shell programming, I run into “corner cases” every now and then.

E.g. in getlyr’s line 7 it warns:

echo -e $(gum style --italic --foreground "#f4b8e4" "'$artist', '$song'")
        ^-- SC2046: Quote this to prevent word splitting.

For more information:
  https://www.shellcheck.net/wiki/SC2046 -- Quote this to prevent word splitt...

Most likely not all that problematic in this application, but it’s good to know about this underlying concept. Word splitting is basically splitting tokens on whitespace, this can lead to interesting consequences as illustrated by this little code:

$ echo $(echo "Hello   World")
Hello World

$ echo "$(echo "Hello   World")" 
Hello   World

In the first case the shells sees two whitespace-separated tokens or arguments for the echo command. This basically becomes echo Hello World. So, echo joins them by a single space. In the second one it sees one argument for the echo command, so echo simply echos this single argument that contains three spaces.

@prologic@twtxt.net Oh yeah, that’s terrible, yuck! Let’s not do it then. :-)

@prologic@twtxt.net As written in IRC, several things turned me off. I don’t have the energy at the moment to wrestle through. :-(

After I stripped off my clothes and turned around, I came to the conclusion that the plan to shower was cancelled at this moment. The faucet had broken right off and was laying in the tub. I noticed that the diameters of the hot and cold water pipes were surprisingly small, didn’t expect that. Since the pipes were broken flush with the wall, I couldn’t even determine if I had to remove the inner our outer threads, well, remains thereof, in order to attempt to repair this mess. Luckily, I was going to see a plumber mate at the christmas tree collection later anyway.

The first thing that came to mind when I woke up was that I didn’t catch the logical flaw in my dream: absolutely no water was coming out of the burst pipes. The whole scenario took place in summer, so the water couldn’t be frozen either.

@prologic@twtxt.net If you’ve got the feed URL in yarnd’s cache, you can easily look up a missing nick. If you can’t find it, just show the URL (or maybe just the domain name to be halfway consistent with this @nick@domain thing that yarnd invented) and be done. It’s really that simple.

When yarnds peer with each other, the odds of actually having come across that feed URL in the past are higher than with traditional clients that only have their local set of subscribed feeds. One additional improvment would be to also look at all the mentions and see if somebody used a nick for that URL and go with that.

Yeah, yarnd currently renders some really weird shit when the mention contains just a URL, but I’d call that a bug for sure.

Personally, I do not like the @nick@domain syntax at all. It looks silly to my eyes. What might have also contributed is the fact of this mentions syntax gotten screwed up so many times by yarnd in the past. But that’s a totally different topic.

@kat@yarn.girlonthemoon.xyz @prologic@twtxt.net So, a burning roll of yarn…? :-D

@kingdomcome@yarn.girlonthemoon.xyz I’m all in!

Hmm, I just noticed that the feed template seems to be broken on your yarnd instance, @kat@yarn.girlonthemoon.xyz. Looking at your raw feed file (and your mates as well), line 6 reads:

# This is hosted by a Yarn.social pod yarn running yarnd ERSION@OMMIT  go1.23.4
                                                         ^^^^^^^^^^^^

Looks like the first letters of the version and commit got somehow chopped off. I’ve no idea what happened here, maybe @prologic@twtxt.net knows something. :-? I’m not familiar with the templating, I just recall @xuu@txt.sour.is reporting in IRC the other day that he’s also having great fun with his custom preamble from time to time.

That “broken” comment doesn’t hurt anything, it’s still a proper comment and hence ignored by clients. It’s just odd, that’s all.

@movq@www.uninformativ.de Very cool!

tt currently supports all three forms: @<nick url>, @<url> and even the illegal @<nick>. The difference between the last two is whether the token in angle brackets looks like a URL or not. Whenever a nick is available, the nick is rendered. In case there is just a URL, it tries to resolve the nick from the subscriptions. If that also does not work, it displays the URL.

@andros@twtxt.andros.dev Even though I’m not an Emacs user, that’s really cool! :-)

@bender@twtxt.net Hahaha! :-D

@kat@yarn.girlonthemoon.xyz Thanks!

@prologic@twtxt.net @movq@www.uninformativ.de Well, the original Twtxt Specification explicitly allows for the short form with just a URL and no nick: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html#format-specification

Mentions are embedded within the text in either @<source.nick source.url> or @<source.url> format […]

I’d just continue supporting it, even though I don’t see it all that often in the wild. I guess more common is the case where just a nick is given, which is illegal. But yarnd users seem to produce it every now and then.

What’s the motivation for deprecation?

@movq@www.uninformativ.de Woohoo, noice! Now you can ship, even sell it! :-D

All kidding aside, even though I never wrote a proper brainfuck program myself, I do like that. :-) Keep it going.

@kat@yarn.girlonthemoon.xyz The early bird… oh wait. :-D

Yeah, @bender@twtxt.net, I absolutely love it! :-D Monty Python just rocks!

This very knight inspired me to make myself a knight helmet with opening visor out of an old washing machine sheet metal years ago for a theater play. It was really great fun, both making the helmet as well as using it during the week in the play as a silly and shady prince who got all his tracts of land by winning dubious games.

I just couldn’t really hear very well in it. And if somebody hit me on the head or just slightly knocked on the helmet, it was incredibly loud. No fine craftmanship by any means and obviously historically extremely questionable at best, but it did the job well enough. One of the running gags was that I had to open the visor when I wanted to talk. Here are some photos in action, you’ll find many more when surfing through the gallery:

• https://wawuwo.de/2016/woche2/montag/017.html#image
  
• https://wawuwo.de/2016/woche2/dienstag/019.html#image
  
• https://wawuwo.de/2016/woche2/mittwoch/156.html#image
  
• https://wawuwo.de/2016/woche2/donnerstag/008.html#image
  
• https://wawuwo.de/2016/woche2/freitag/036.html#image In one lunch break my page and I decided to dress up and play a game of dice against the kids. However, we used badly cogged dice. We just added a few dots of paint on one of the two dice, so that it had two fours, two fives and two sixes or something like that. I always told my opponents: “You can choose whatever dice you want. Except for the red one, that’s my lucky dice!” As well-behaved children, they then selected the blue, unbiased one. And usually lost. However, I remember there was one kid that beat me with four sixes in row. :-D Although we thought, we make it halfway obvious that this game is truly not fair, it took them extremely long to figure out that we had messed with my lucky dice. When they finally did, they got super angry. Some of them were on the brink of beating me up. That was really nice to see their sense of justice kick it. :-)
  
• https://wawuwo.de/2016/woche2/freitag/169.html#image

@movq@www.uninformativ.de Woah, that’s insane! Yeah, I wanted to take it easy as well, but then suddenly got 9:30 hours on the clock… :-/

Vacations were great, it took me five attempts this morning to enter my disk encryption password. :-D

An hour later and I have glued together a new batch of cardbord boxes. I’ve cut out the blanks several days ago, though. Easy upcycling project: