Just threw this RSS feed into Newsboat. The titles suck, but I hope the content makes up for it. :-)
@movq@www.uninformativ.de Speaking of fog, a workmate showed me his view out of the window today and you couldnāt even see a hundred meters. Looked really nice! :-) We actually had a little bit of sun over here.
@movq@www.uninformativ.de Woah, that sun from satellite SDO is fucking sick! https://social.bund.de/system/media_attachments/files/113/859/065/836/106/300/original/95b43f7a0086476d.jpeg
I havenāt read the entire specification, but I think there is a fundamental design problem. Why would someone put an encrypted message on a public feed that is completely useless to everybody other than the one recipient? This doesnāt make sense to me. It of course depends on the threat model, but wouldnāt one also want to minimize the publicly visible metadata (who is communicating with whom and when) when privately messaging? I feel there are better ways to accomplish this. Sorry, if I miss the obvious use case, please let me know. :-)
Clouds are hiding the planets right now, but the sky was slightly on fire before: https://lyse.isobeef.org/abendhimmel-2025-01-20/

This is an absolutely amazing talk about fixing a satellite in space. Totally worth watching, highly recommended. Super great engineering! Iām blown away, this is sooooo cool! https://media.ccc.de/v/38c3-hacking-yourself-a-satellite-recovering-beesat-1
@movq@www.uninformativ.de Oh yeah, nice! I gotta have to check tomorrow. I keep forgetting.
@kat@yarn.girlonthemoon.xyz Only scp/rsync for me. :-) But I remember there is one server that only provides SFTP access. :-/
@andros@twtxt.andros.dev Nope, unfortunately not. I took a look at Lisp last year (I think I used sbcl), but I havenāt done anything really useful with it. I still want to give it a proper go some time in the future. I do like how flexible it can be. Rather simple, but powerful basic concepts.
Whatās your favorite dialect?
@kat@yarn.girlonthemoon.xyz I approve! Thatās how I learned HTML (version 4 at the time and XHTML shortly after) and making websites, too. Some of them are still made like this to this day. Hand-written HTML. Hardly any <div> and class nonsense. I canāt remember with which editor I started out with, but I upgraded to Webweaver (later renamed to Webcraft) quickly. Yeah, this were the times when there was just a single computer for the whole family.
Free hosting on Arcor, Freenet and I donāt know anymore how they were all called. Like this author, I uploaded everything via FTP. Oh dear, when was the last time I used that? And I had registered plenty of free .de.vu domains.
Being on Windows at the time, everything was ISO-8859-1 for me. No UTF-8, I donāt think Iāve heard about it back then.
Later, I wrote my own CMSes in PHP. Man, were they bad in retrospect. :-D Of course, MySQL databases were used as backends. I still exactly know the moment I read the first time about SQL injections. I tried it on my own CMS login and was shocked when I could just break in. The very next thing I did was to lock down everything with an .htaccess until I actually fixed my broken PHP code. Hahaha, good memories.
I swear by Atom or RSS feeds. Many of my sites offer them. I daily consume feeds, theyāre just great.
@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! :-)
@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. :-)
v1.23.4 will there ever be a v1.23.45678? š« š¤”
@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.
code { white-space: pre } in their CSS themes to render things as they're supposed to look like.
Well, I stand corrected, pre-wrap even! https://git.mills.io/yarnsocial/yarn/pulls/1186
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.
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.
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
@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.
