I was wondering why all the twt hashes in my replies today were still so short. I was ahead of the times. The Twt Hash v2 Epoch only begins next month.

@itsericwoordward@itsericwoodward.com Haven’t noticed anything either. These request numbers are well below some other software. :-)

It’s not that much traffic, of course. One hit per second on average. (Plus the images.) The nasty bots are much worse. 😅

We’re at close to 20k hits now, but it has slowed down considerably. Nobody cares about page 2. 😅

@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! 🎉🎉🎉

Yay finally fixed some of those annoying “Mark as Read” behaviours/bugs 🐞

@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 🤔

@movq@www.uninformativ.de TLs is cheap, we built hardware encryption modules for AES-256 which TLS still uses so you’re fine 😅

@arne@uplegger.eu Indeed. I’m glad that it’s all just static HTML. The most expensive part about this is probably TLS. 🤷‍♀️

@bender@twtxt.net

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 👌

Upvoted, @movq@www.uninformativ.de! See: https://news.ycombinator.com/item?id=48331329

@itsericwoodward@itsericwoodward.com noticed absolutely nothing. Happy developing!

@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 👀

@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!