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 👌
Apologies to anyone who’s seen an uptick in twtxt pings from me today… I’ve been working on shoe-horning my twtxt reader (TwtStrm) into my editor (TwtKpr, aka the 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 🙂).
@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.
@movq@www.uninformativ.de Oh yes, very cruel. Absolutely. But also beautiful sometimes.
@movq@www.uninformativ.de Wow, quite the background noise! I like the birds, though. :-)
@lyse@lyse.isobeef.org love them! I hunt for those here. I enjoy watching it as it happens. Never that red, though.
@lyse@lyse.isobeef.org I notice a theme here, but can’t quite place my finger on it… 🤭
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
I wasted my entire weekend on the writeup. If you have way too much time to spare and also are interested in a bug analysis of a software that you don’t even use, I have you covered: https://lyse.isobeef.org/newsboat-time-parsing-bug-analysis/
@movq@www.uninformativ.de that was lovely! I especially liked the rain. I truly am a sucker for rain!