#catsoftwtxt

@lyse@lyse.isobeef.org Oh god, yeah. In other words: Devs need to think about who their target audience is. 😐

@movq@www.uninformativ.de Hahaha, great timing! :-D I love your article and agree with almost all your points.

On the AI changelog part, though, I’d rather recommend to just not have a changelog at all.

Another important thing for me is the deprecation notice section. What do I need to look out for in the future? Should I start to migrate to another API soon? Even right now? Or does it have time?

While going through these terrible GitHub release pages, I also found these “New Project Contributors” sections (yeah, for that, they found the time to make a section) annoying. Don’t get me wrong, sure, credit where credit is due. But come on. Soooooo much space for an inefficiently formatted (and also unsorted) list. At least it was easy enough to skip over it.

And then, there are also these changelogs or rather notice documents in general that are infested with multicolored emojis all over the place. My brain’s spam filter kicks in and shoves everything to /dev/null immediately. It’s especially a thing at work.

In my previous work project, we also used the Keep A Changelog Format. That was great. You wouldn’t believe how often I resorted back to that document. At least twice a week, often several times a day. I was very glad that we put in this effort. Of course, writing the changelog took its time, but it was worth every minute and more. Reading a many months old item, it was immediately clear. I was our best customer in that regard.

Now, it’s just the same auto shitshow with MR titles in a rolling date-versioned release scheme. It’s just our team who has to deal with that, though. I think I’m the only one who is not a fan of it.

@prologic@twtxt.net As have I. 🤔 I mean, since I left GitHub, I got basically 0 pull requests anyway.

Even during my time using GitHub, I noticed that “drive-by PRs” are rarely a good idea. People don’t really know/understand the code or the design principles/goals, so I often turned down PRs. Or I accepted them and was grumpy afterwards. 😅

What does work is having a team of maintainers/devs. The only question is: How do you build such a team if you don’t accept PRs? That’s going to be the interesting part.

I am a bit tired and unfocused this morning. I just typed npm ruin dev into the terminal, maybe some foreshadowing?

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

#catsoftwtxt

#catsoftwtxt

-¡Nadie me quiere dar mimos!-
#catsoftwtxt

#catsoftwtxt

@klaxzy@klaxzy.net twtstrm/0.4.0 is from Eric. The getwtxt-ng/dev seems to be this.

what is the user-agent name of the crawler that pulls the tweets here on twtxt.net? i am seeing getwtxt-ng/dev and twtstrm/0.4.0 in the logs

Je pige pas les maths derrière, mais apparemment il est maintenant […] 🔗 https://yom.li/notes/20260428123534 🔖 https://smsk.dev/2026/04/26/ai-cannot-self-improve-and-math-behind-proves-it/

@klaxzy@klaxzy.net Check https://twtxt.dev/clients.html

https://secureblue.dev/

¡Hoy cumplo 2 añitos!
#catsoftwtxt

#catsoftwtxt

I installed Alpine Linux on my laptop. I’m pissed that Devuan wouldn’t boot after installing. Msg to Devuan devs: terrible UX after “successfully” installing when you see “grub>”.

Hey all my dear twtxters! Again, please have a look at https://git.mills.io/yarnsocial/twtxt.dev/pulls/28 so that we can button the Twt Hash v2 Extension up soon. Love to get some feedback, comments, questions, doubts, critiques, improvements, etc.

@rdlmda@rdlmda.me https://twtxt.dev/clients.html

@movq@www.uninformativ.de just use https instead:

git clone https://git.mills.io/yarnsocial/twtxt.dev.git

Let’s finalize https://git.mills.io/yarnsocial/twtxt.dev/pulls/28/.

@rdlmda@rdlmda.me

Replies aren’t actually broken, I just… need to add myself to the follow list?! That’s quite counter-intuitive and (IIRC) not mentioned in the docs. But… It seems to be working now, which is nice (I still don’t know how webmentions and webfinger works, so can’t speak about this so far)

yarnd (what runs here at twtxt.net) actually does this automatically by default. I think it’s just an implementation detail to be honest. There’s nothing about this in the specs over at https://twtxt.dev

-¿Qué viene quién y cuándo?-
#catsoftwtxt

#catsoftwtxt

@rdlmda@rdlmda.me You need to use the RFC3339 format. I would recommend you read the specs at https://twtxt.dev – This is what is used by many moden clients these days 😅

#catsoftwtxt

I’ve created a blog at bearblog.dev, linked above

Hmmm, that’s a pity. I never realized that before. The following Go code

var b bool
…
b |= otherBool

results in a compilation error:

invalid operation: operator | not defined on b (variable of type bool)

I cannot use || for assignments as in ||= according to https://go.dev/ref/spec#Assignment_statements. Instead, I have to write b = b || otherBool like a barbarian. Oh well, probably doesn’t happen all that often, given that I only now run into this after all those many years.

Trying an experiment. Created a Github repo for mu over at https://github.com/prologic/mu as a social experiment to see if we can maintain a tailored Github docs-only repo of a project, see if it gets any interest 🤔

@prologic@twtxt.net broken link. Correct one is: https://mu-lang.dev/

Have finally put together the beginnings of a site for Mu (µ) https://mu-lang.dev 🤞 #mu #mu-lang

Fark me OS Dev is hard 🤣

Solo tú y yo, por siempre
#catsoftwtxt

#catsoftwtxt

Bitcoin had a lot of potential, but It won’t fulfill it’s purpose because the Devs are little girls who are afraid of The state. in fact, The coin is going to become The state’s coin, The more effecient The state is The more valuable is it’s coin, Therefor The freedom you’ve hoped for was murdered becuase you’ve abandoned The project in it’s first steps, satoshi.

CatGPT
#catsoftwtxt

#catsoftwtxt

@prologic@twtxt.net AI is slot machines for coders:

• “Before starting tasks, developers forecast that allowing AI will reduce completion time by 24%. After completing the study, developers estimate that allowing AI reduced completion time by 20%. Surprisingly, we find that allowing AI actually increases completion time by 19%–AI tooling slowed developers down.” https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/
  
• “Stack Overflow data reveals the hidden productivity tax of ‘almost right’ AI code”: https://venturebeat.com/ai/stack-overflow-data-reveals-the-hidden-productivity-tax-of-almost-right-ai-code
  

The same intermittent reward operant conditioning that gets people addicted to gambling and thinking that if they follow certain rituals they’ll win “next time” drives people’s beliefs that AI tools are making them more productive when they’re making them less productive. I’m going to guess that a side effect of this is that people think they’re typing less when in the longer term they’re typing the same amount or more when you factor in the productivity loss (as far as I’ve read the studies don’t measure this so I’m only guessing).

People are also being rapidly de-skilled by this technology: the more they use it, the more their actual skills atrophy. “Continuous exposure to AI might reduce the ADR (adesoma detection rate) of standard non-AI assisted colonoscopy, suggesting a negative effect on endoscopist behaviour.” (science speak for saying that radiologists get worse at seeing tumors in scans once they’ve used AI): https://www.thelancet.com/journals/langas/article/PIIS2468-1253(25)00133-5/abstract

Nobody who cares about the future should be using this stuff for anything.

@bender@twtxt.net Just a donations thiny I knew about from years ago that I never setup properly. Now an acceptable form of donation on my prologic.dev site 👌 (if anyone ever does that is!)

yakumo.dev is finally done for, November 26, 2025 in UTC time.

So long… I won’t be missing it though

Hm, so regarding the hash change:

https://git.mills.io/yarnsocial/twtxt.dev/pulls/28

How about 2026-03-01 00:00:00 UTC as the cut-off date? 🤔

First Dates: Baldo. 2 años. «Ronronea conmigo durante toda la noche.»
#catsoftwtxt

All my newly added test cases failed, that movq thankfully provided in https://git.mills.io/yarnsocial/twtxt.dev/pulls/28#issuecomment-20801 for the draft of the twt hash v2 extension. The first error was easy to see in the diff. The hashes were way too long. You’ve already guessed it, I had cut the hash from the twelfth character towards the end instead of taking the first twelve characters: hash[12:] instead of hash[:12].

After fixing this rookie mistake, the tests still all failed. Hmmm. Did I still cut the wrong twelve characters? :-? I even checked the Go reference implementation in the document itself. But it read basically the same as mine. Strange, what the heck is going on here?

Turns out that my vim replacements to transform the Python code into Go code butchered all the URLs. ;-) The order of operations matters. I first replaced the equals with colons for the subtest struct fields and then wanted to transform the RFC 3339 timestamp strings to time.Date(…) calls. So, I replaced the colons in the time with commas and spaces. Hence, my URLs then also all read https, //example.com/twtxt.txt.

But that was it. All test green. \o/

Diferencia entre gato poralizado y no polarizado
#catsoftwtxt

@prologic@twtxt.net this one? https://twtxt.dev/assets/img/twtxt-logo.svg Other than being “circlish” I don’t see any relationship. 😅

@prologic@twtxt.net I prefer something like the logo on https://twtxt.dev, for example, instead. But hey, it is your pod, have fun!

-Yo no estoy en peligro, Skyler. Yo soy el peligro. Un sanguinario depredador se abalanza sobre un lindo minino, ¿y tú crees que ese soy yo? No. ¡Yo soy el que salta!-
#catsoftwtxt

Soñando que vence a Scar
#catsoftwtxt

Android shopping list apps disappointed me too many times, so I went back to writing these lists by hand a while ago.

Here’s what’s more fun: Write them in Vim and then print them on the dotmatrix printer. 🥳

And, because I can, I use my own font for that, i.e. ImageMagick renders an image file and then a little tool converts that to ESC/P so I can dump it to /dev/usb/lp0.

(I have so much scrap paper from mail spam lying around that I don’t feel too bad about this. All these sheets would go straight to the bin otherwise.)