You know what this is?
https://movq.de/v/ef1674f6c5/bird-bird.webp
A BIRD bird! 😅
I got it as a gift from a very friendly coworker and she, in turn, got it from Maria Matějka. 😃
@bender@twtxt.net Ugh, I don’t know. I’m having a long vacation now and I try not to think about this topic anymore. 🤣
@movq@www.uninformativ.de what are your thoughts after reading it?
Response by the author of rsync: https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0
@movq@www.uninformativ.de Yes.
Maybe management should replace itself with AI…
@movq@www.uninformativ.de It’s the “Lyse types the entire HTML by hand” generator. Yes, no kidding. I write articles so rarely, that I can do that once in a while. It’s fun to some degree, but also not.
After some time, I finally recorded some Vim macros to insert <b>…</b>, <var>…</var>, <span class=s>…</span> etc. around the tokens. This helped a little bit. But I was still questioning my mental state doing it like that. I also had to fix a bunch of the end tags by hand, because the word movement wasn’t enough or the end movement went too far. Quite the annoying process for sure.
But I think the HTML looks a wee bit nicer and is maybe even semantically a little bit better than having only <span>s everywhere. I find the <span class="whatever"> just soo awfully long. Of course, I never look at the code again, but knowing, that e.g. there is a <b> and it saves so many bytes in comparison, makes me happy. It is a more elegant solution in my opinion. Not by much, but better nonetheless. It’s a matter of simplicity. Admittedly, even I can’t avoid the <span>s alltogether. Oh well. On the other hand, I’m sure that this does not make any difference whatsoever. I bet, nobody and nothing, like a screenreader, analyzes the HTML for that, where this would be truly useful.
Oh! Maybe text browsers, though. It just occurred to me while composing this reply. :-) Haha, I lost my bet quickly. w3m picks up at least the <b> for keywords and builtin types, <u> for filenames and <i> for comments. Yey. No different styles for <var> and <mark>, unfortunately. elinks only renders the bold. It’s cool that I had the right intuition right from the beginning, despite being unable to pinpoint it. :-)
All the <span> hell with common syntax highlighters is a downer for me that keeps me from looking more into them. If I wrote more articles, I might rig something up with Pygments. At least that’s somehow positively connotated in my brain. Not sure if it actually deserves it, but I dealt with that in some loose form (can’t even remember) years and years ago. Apparently, it wasn’t too terrible.
To prepare the table of contents, I used grep and sed with some manual intervention in the end. The entire process can be improved. Absolutely.
You wrote your own site generator, didn’t you?
@movq@www.uninformativ.de Nice find!
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
@lyse@lyse.isobeef.org By the way, which site generator are you using? I kind of miss having code blocks with syntax highlighting and that generic yellow highlighting thing is pretty cool, too.
@lyse@lyse.isobeef.org lol, “garbo” 😅 Took me a moment. 🤣
@bender@twtxt.net Hahaha! :-D
@garbo@www.uninformativ.de What a story! :-D
@kiwu@twtxt.net I like your enthusiasm. Go, go, go! :-)
@bender@twtxt.net Hahaha! :-D
@bender@twtxt.net That certainly sounds much better in English, yeah. 😅
@movq@www.uninformativ.de hahahahaha! I’d say “Princess Grim Reaper” is more suiting. 😂
@bender@twtxt.net It started out as me calling myself “Princess Valium” because I’m so tired and braindead today, but then someone misheard that because a garbage truck drove by, and, so … one thing lead to another. 🤪 Sadly, it kind of fits, because I’m often the one who cleans up shit. 😬
@bender@twtxt.net LOL 😂
@movq@www.uninformativ.de but why? Are they that mean?! 😅
@kiwu@twtxt.net welcome, new slave! Err, I meant, beloved employee! 😅
@prologic@twtxt.net I do! I paginate usually 10 times on HN. Their algo is so messed up (but it works, I guess) that not doing that will make me miss a lot of good, interesting, things.
@kiwu@twtxt.net In-cred-ib-ly tired. 😂
express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I've added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).
@prologic@twtxt.net @bender@twtxt.net Thanks! Yeah, it already supports Twt Hash via twtxt-lib (both v1 and v2, when the time is right), plus most of the other features (multiline, user-agent, and metadata), and I’m working on (re-)implementing threading, mentions, and hash filtering (to make conversations easier to follow).
Here’s a current snapshot of my local version, in case anyone is interested:
@lyse@lyse.isobeef.org LOL. Always ahead of times! Lyse, the man from the future! Sic mvndvs creatvs est!
express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I've added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).
@itsericwoordward@itsericwoodward.com Haven’t noticed anything either. These request numbers are well below some other software. :-)
@movq@www.uninformativ.de Interesting read! The current state is already a very great achievement. I felt honored being able to already have followed your development along here on twtxt. :-)
That’s a cool clock, I should remind myself of my working time, too.
@bender@twtxt.net The good thing is that it’s already pretty battle-tested. 😅 There was this dumpster fire a few years back: https://news.ycombinator.com/item?id=31114554 This was on their front page for quite a while, just look at the number of comments … 😂
@prologic@twtxt.net woot! 🎉🎉🎉
@bender@twtxt.net Yes, but I consider this to be a flaw in the human species. Think about it, what good does it serve? What possible reason do we have to have such traits today? Survival of the fitness? pffft 😅
@movq@www.uninformativ.de LOL. At least now you know your infrastructure and web server can handle some traffic. Consider it a test, in addition to the fleeting recognition. 🤣
@prologic@twtxt.net that possible in any profession. Contrary to what @prologic@twtxt.net’s think, I don’t think it is a human weakness. That some people are absolute and despicable assholes? Yep, I agree on that.
@rrraksamam@twtxt.net No 🤣 I think it’s a human weakness, someone born in the genes of some 🤔
tail -f access.log looks like a Matrix screensaver at the moment. Whoooooosh …
@movq@www.uninformativ.de TLs is cheap, we built hardware encryption modules for AES-256 which TLS still uses so you’re fine 😅
tail -f access.log looks like a Matrix screensaver at the moment. Whoooooosh …
@arne@uplegger.eu Indeed. I’m glad that it’s all just static HTML. The most expensive part about this is probably TLS. 🤷♀️
oh, I knew it wasn’t you. It is just nice to see your hobby was noticed. :-)
Ah, I see! 🤗
@bender@twtxt.net Doing tail -f access.log looks like a Matrix screensaver at the moment. Whoooooosh …
@bender@twtxt.net … boom, 5500+ hits on that blog post. 🤣 Should I start monetizing this shit?! 🤪 (Don’t worry, I won’t. German law gets super annoying if you do that kind of thing.)
I mean, this is pretty awesome!

@movq@www.uninformativ.de oh, I knew it wasn’t you. It is just nice to see your hobby was noticed. :-)
@bender@twtxt.net Oh, well, thanks, I guess? 😅 (This “zdw” person isn’t me. I don’t even have an account at HackerNews. 😅)
@bender@twtxt.net upvoted too 👌
express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I've added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).
@itsericwoodward@itsericwoodward.com noticed absolutely nothing. Happy developing!
express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I've added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).
@itsericwoodward@itsericwoodward.com Excited to see twtxt tooling in the Node ecosystem! Any plans to implement the Twtxt v2 extensions? Things like Twt Hash + Subject (proper threading), Multiline, etc. — all documented at https://twtxt.dev 👀
express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I've added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).
@itsericwoodward@itsericwoodward.com All good here 👌
@bender@twtxt.net Thank you, we think so too.
I’m glad you like it!
@itsericwoodward@itsericwoodward.com that second one… 😍! Shadow is such a handsome boy!
@movq@www.uninformativ.de Hahaha, a ride indeed. Exactly, this affected each and every Atom feed and only Atom feeds. All RSS feeds worked like nothing ever happened. This std::string to time_t to std::string to time_t dance only happens for Atom feeds. RSS feeds, on the other hand, go right from std::string to time_t and be done. That’s precisely what the second option is aiming to propose for Atom feeds, too.
I will clarify that tomorrow in the article.
It’s very interesting what kind of quirks accumulate in software over the years. Especially quirks, the basically noone knows of anymore. Until something explodes and gets rediscovered. Luckily, that doesn’t happen all that often.
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
@lyse@lyse.isobeef.org Oh, nice. That was quite the ride. :-) And all that because of locales. 😳
But, did I understand that correctly? All Atom feeds were broken, right? Because they all use that same code path with that strftime/strptime dance in it?
@bender@twtxt.net No way, impossible! Which pattern could you have possibly spot? :-D
@bender@twtxt.net Doesn’t happen often. And when it does, it’s a matter of just a few minutes.