@bender@twtxt.net Iâll think about it. :-)
I rode my bicyle to the scout flea market setup a few weeks ago when I had to stop to admire the morning sun lighting up the fields. https://lyse.isobeef.org/morgensonne-2026-05-08/ Of course, these photos donât do justice at all.
@movq@www.uninformativ.de It already broke successfully: https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390
@bender@twtxt.net You mean to make it all blank? ;-)
@bender@twtxt.net Welcome to our bot club!
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
This is also why @bender@twtxt.netâs Notes feed was unaffected. Itâs an RSS feed.
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
Aha, yesterdayâs newly added support for LC_TIME to render localized timestamps also broke the feed parsing with my LANG=de_DE.UTF-8 and LC_CTYPE=de_DE.UTF-8 environment. :-)
Atom feeds make use of RFC 3339 timestamps. They are first converted into RFC 882 timestamp representation, which is the one that RSS feeds use. However, this conversion now results in localized RFC 882 timestamps, which cannot be parsed into Unix timestamp numbers via curl_getdate(âŠ). I bet that it doesnât know about the localization at all and expects English month and weekday names. Looking at its docs, I reckon that function was selected because of its myriad of supported timestamp formats: https://curl.se/libcurl/c/curl_getdate.html RFC 3339 is not included, though, hence the transformation up front.
The intermediate Item objects in the parser domain use std::string for the timestamp representation. This isnât all that silly, because Newsboat supports all sorts of different feed formats with different timestamp formats. These RFC 883 timestamps are centrally parsed into time_t.
Speaking of time: Itâs time to go to bed after this late bug hunting fun. :-)
@movq@www.uninformativ.de I really like your style of writing, btw. Itâs much calmer and less aggressive then mine. :-) When I turned my bullet points into paragraphs, I got a bit mad in the process.
Sure, feel free to include anything you want. Regarding citing, this is where twtxt falls short in my opinion. Especially with feed rotation, classic links die quickly. Message hashes only help so much. Nobody outside the twtxt universe knows how to deal with them. So, not perfect for inclusion on a web page. Linking to a thread or message on some yarnd instance might be the more user-friendly option. But the disadvantage is that itâs âjustâ a mirror, not the primary or original source. In all reality, this could be considered splitting hairs, though.
I should have probably written a proper article. That would have given me time to review the result more carefully, too. ;-) Perhaps thatâs something for the future. But honestly, Iâm not sure if I really want to waste my time and energy on that subject. So many other fun or useless things come to mind right away that I could do instead. 8-)
So, yeah, do whatever feels best to you. I donât mind being cited or linked, but I also donât mind not to be cited or not to be linked to. :-D Not a helpful answer, I know. Sorry. ;-) But anyway, thanks for asking, mate! I do appreciate it.
To finish my thought, linking to my frontpage is probably also useless, since I deliberatly do not have a table of contents there. In fact, my entire frontpage is rather silly.
@movq@www.uninformativ.de Oh, I understand exactly what you mean. :-) I fully agree with you. And it also completely puzzles me why only so few people share our view.
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
On further examination, all the articles have the same timestamps. Whenever the feed was fetched. :-O
noai.html page. Apart from the global updated field in my feeds (that one got changed), everything else should be stable, though.
@movq@www.uninformativ.de Thanks. I noticed the <updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
On some YouTube feed <entry>s, I noticed updated <updated> fields showing todayâs timestamps. But unless there is no <published>, the <updated> is not even considered. I verified that in the source code. Yet, all the affected articles in Newsboat show todayâs timestamp, not the years old publication timestamp. I generate the YouTube feeds from the original feeds myself once a day, so I doubt that this is cause by some YouTube shenanigans.
Very weird, it doesnât make any sense at all. What is going on here? O_o It doesnât appear that I have duplicates in the database either.
You didnât change your Atom feed by any chance yesterday or today, @movq@www.uninformativ.de? Not only do I have a metric shitton of ânewâ old items in my YouTube feeds, but also a bunch of your old articles are shown as new.
I fear that this is a Newsboat bug. I rebuilt it yesterday from master.
Of course, @movq@www.uninformativ.de! Most of my points are also included in your list.
First of all, programming is what I really do enjoy the most. So, it doesnât make any sense at all to not do this anymore. âBut you could use your now free time to do something much cooler and more valuable!â, others might reply. Fuck no, I donât want to waste my time with other shit that doesnât fulfill me, why on earth would I want to do that?
All this hallucination reduces quality badly. In my experience, itâs also happening much more rapidly than I expected. Even though developers are still supposed to own and understand whatever has been generated under their name and even be responsible for that, the sad reality is that teammates often blindly trust the AI output. âBut I asked the AI and it told me that $this was impossibleâ, âIâve no idea either, but the AI just generated itâ are responses I get more often. What really makes my angry is when I point out a flaw and suggest an alternative and this is the reaction. It happened several times that just trying it out and seeing it clearly work to proof my point only took me half a minute, but people still did something handwavy else instead.
The learning effect is drastically reduced. The more time I spend on a topic, the better the odds that whatever I learned actually makes it over into long-term memory. Itâs like if a collegue just says âdo it like thatâ or âthis solves your problemâ, but neither explains the why or how. Somehow, people are still convinced that itâs a completely different story when you replace the human counterpart with a computer program in this equation.
Skills are unlearned. Itâs like with automation in general, just much worse. You end up in a state where youâve no clue how anything works under the hood or how to actually find out important information that are needed to solve your problem. Youâre screwed when a process breaks out of the blue. Even though it can become also rather terrible, with classical automation youâre typically still be able to decipher how exactly the thing was supposed to do something.
The energy consumption is sooo high, I absolutely do not want to be a part in burning down our planet. Iâm sure I find (and probably have long found without knowing) other ways to contribute to worsen our climate crisis.
The scraper part is already covered in detail in your list. :-)
Iâm convinced that license and copyright violations are only played down or even refused entirely because companies want to make big money quickly. With the work of others of course. Their double standards are obvious, they still try to actively keep their own stuff secret and out of any training sets. At most for internal use only. Virtually noone in charge is interested in good long-term solutions. Short-term for the win, when disaster eventually strikes, the causers are long gone, the responsibilities in other hands.
Vendor lock-in is something that lots of folks are only realizing very slowly. Itâs completely crazy to me. This drug dealer routine should be well-known by now. Itâs fucking everywhere. Yet, people are always surprised when they found themselves caught in it.
Adding new AI stuff only increases complexity. But complexity is the enemy that everybody should fear and reduce as much as possible. Of course, this is not limited to AI at all. And everywhere I look around, people in charge looooove to make things way more complicated than they ever need to be. Yet, simplicity is the real art and much harder to achieve.
I donât understand why we have to go back full force to the ambiguity of natural languages. This alone should be more than enough to realize what a stupid idea all that is. Linked to that is that the âinstruction setâ is interpreted differently with newer model versions. I mean, is has to be. Why else would somebody want to upgrade in the first place than to get more Powerfulâą Featuresâą?
Some people argue that with AI the democratization is empowered. However, in my view, the exact opposite is the case. Models are getting so large that you can basically not run them locally or even train them. So, you have to rely on whatever the vendor offers you and runs for you. In the end, this only gives the owners more power, the multi billionaires. Not exactly what I understand by democratization.
Finally, technology assessments are missing completely. Or they are faked such that mostly only the (questionable) benefits are listed. But all the negative impact is just ignored.
Letâs keep some popcorn around for when this all explodes. :-)
@arne@uplegger.eu @movq@www.uninformativ.de Typically, I use âIâ. But also âoneâ and, less common, âyouâ.
@movq@www.uninformativ.de Yes, this is the tricky bit for sure.
Of course, they say that totally convinced. Until it eventually explodes in their faces and let others clean up after themselves.
@itsericwoordward@itsericwoodward.com @bender@twtxt.net @prologic@twtxt.net Hahaha, itâs working fine in mine. But I cannot use spaces in the nickname. :-)

@movq@www.uninformativ.de @bender@twtxt.net Couldnât agree more. Iâll check my list tomorrow that I started a few weeks ago.
@movq@www.uninformativ.de If you really like to, you can try to negotiate with your employer that you can leave earlier. At least some mates were successful in that. I mean, itâs also in the companyâs interest to not have to pay someone who has already mentally resigned long ago.
And on the bright side, you donât even have to hand over anything. Your boss doesnât have to look for a successor, so they can just let you go even sooner. This AI shit will simply continue whatever you did, no problem!!
Itâs so crazy. I should probably also look for something else. :-(
@Little-Eric-{{first_name}}@itsericwoodward.com Hahaha, will do! :-D
@movq@www.uninformativ.de Hahaha, very nice! :-D
@itsericwoordward@itsericwoodward.com @bender@twtxt.net Dang it, I missed it, too.
@itsericwoordward@itsericwoodward.com Confess, you just registered as {{first_name}}!
Nobody checks their e-mail templates. And even if they do, they only look at the HTML part. The plain text part is useless more often than not. Granted, this is the subject.
@movq@www.uninformativ.de I only had 3.5â disks.
@movq@www.uninformativ.de Cool! Letâs look for 57 61 6C 64 6F.
@movq@www.uninformativ.de Congratulations! I also was a LAMP dude back in the days. Thatâs all we had as kids without money. :-)
@movq@www.uninformativ.de I just changed the bindsym directly in my i3 config. But Iâm looking forward to learn a few new tricks. :-)
@bender@twtxt.net This shit is back. But with SSHFS instead of SMB now. SMB is still fucked for no reason. Letâs see, when it explodes.
I should have changed the key binding from Print to Shift+Print a long time ago to launch import and upload the screenshot to my server. I was constantly hitting that stupid key on accident when I actually wanted to press [AltGr].
If I only could map a key binding to slap these damn ThinkPad T15 keyboard layout designers at Lenovo remotely in the face. Seriously, who in their right mind puts Print (in German Druck) between AltGr and Ctrl at the bottom row to begin with?! Exactly. Nobody. What a horrible location.
@kiwu@twtxt.net Wuuiii, what to do with all this free time suddenly!? Wait, what? Free time? Nah, nevermind. Now, the time begins where it gets even worse once you start a fulltime job. Congratulations, mate! :-D
@movq@www.uninformativ.de Donât worry, the agents will forget everything for them. EhhâŠ
@movq@www.uninformativ.de That certainly paid for itself.
@movq@www.uninformativ.de Oh, great!
@arne@uplegger.eu In der Tat ein Klassiker. Mjam, mjam!
Interesting read on the ECONNRESET saga, @movq@www.uninformativ.de. Thanks for the writeup! <3
Welcome @tftp@tilde.town, I just found you in my access log. :-)
@movq@www.uninformativ.de Oh, thatâs cool! Un- and redo are absolutely valuable features.
@movq@www.uninformativ.de I fear that you are right.
I just wanted to look up 9V block battery prices online and these automatically generated descriptions are getting dumber by the minute:
Datum der Erzeugung: Verfallsdatum minus 7 Jahre
(Date of manufacturing: expiration date minus 7 years)
Or look at this one:
Die leistungsstarke 9 V-Block E Batterie, auch 6LR61 genannt, eignet sich besonders gut fĂŒr Taschenlampen, Radio oder Kinderspielzeug, die einen gleichbleibenden Strombedarf haben. Ihre max. Spannung betrĂ€gt 1,5 V.
(The high performance 9 V block E battery, also known as 6LR61, is particularly suitable for torches, radio or childâs toys, which have a steady power demand. Its max. voltage is 1.5 V.)
The battery is best suited for⊠devices where it fits. No shit, Sherlock! Has anyboy ever come across 9V block torches? O_o I havenât.
Our storage box is not reachable for hours, the support response is unhelpful to say the least. Letâs see how long it takes them to actually fix this. Until then, no photo galleries etc. available.
@movq@www.uninformativ.de 100% agree. Weâre driving straight into a wall at full throttle. Doing it with a clear warning.
@movq@www.uninformativ.de Apropos shit: I did not know about the history of ScheiĂtag. https://en.wikipedia.org/wiki/Schei%C3%9Ftag
Oh no, speedy recovery, @movq@www.uninformativ.de! I was down for one day on Saturday. Vomiting through the nose. Not entirely sure what that was, but I reckon something in the food poisoning or sunstroke realm.
@movq@www.uninformativ.de Oh my goodness, hahaha!
To be fair, it depends on your threat model. And I believe itâs very safe to bet that most probably donât have one. Nor even remotely know what that is. So, itâs plenty good enough for them.
With that new to me detail on top, thereâs even less incentive to look at this Matrix hype more closely.
@movq@www.uninformativ.de Und da konnte ich nicht widerstehen und hab die Folge doch sogleich angehört. Herrlich, sehr kurzweilig, spannend und lehrreich. In der Tat ganz schön viele Arschgesichter, hihihi. ;-)
@movq@www.uninformativ.de Oh, cool! Holgi hab ich schon jahrelang nimmer gehört (allgemein Podcasts), das sollte ich schleunigst wieder Ă€ndern. Diese Folge scheint mir als Wiedereinstieg nach dem arbeitsreichen Wochenende bestens geeignet. Insbesondere die âHolgi ruft anâ-Reihe hab ich in sehr guter Erinnerung.
@bender@twtxt.net @movq@www.uninformativ.de Haha, nice. Yeah, I also only know older Giselas. Not sure why that name fell out of fashion this dramatically, though. Be that as it may, this hot greenfinch girl will help to repopularize it again!
@prologic@twtxt.net Yeah, almost everybody sells their soul to some form of devil. So did I. :-D
@bender@twtxt.net Thank you. I just got very lucky, though. Anyway, let me introduce you to Gisela. :-)
@movq@www.uninformativ.de @bender@twtxt.net Yeah, super sweet. :-) I was lucky to capture this beautie again today: https://lyse.isobeef.org/gruenfink-2026-05-06/