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.)

Oh, and I forgot (because I thought it was obvious, my bad), set a nick, and a url at the very minimum on your feed. See “Metadata Extension”.

@threatcat@tilde.club unwritten etiquette (by me, and for me, but one can hope, right?).

• Proper grammar (in any language).
  
• Correct capitalisation, and punctuation.
  
• Subject extension support.
  

Anything else doesn’t matter. ☺️

PR to clean up some unwanted specs and cleanup some invalid/bad references. 🙏

#catsoftwtxt

-¿Y… sueles acurrucarte mucho por aquí?-
#catsoftwtxt

Disfraz de Halloween 🎃 : ojos flotantes
#catsoftwtxt

¡Feliz Halloween 🎃 🧛!
#catsoftwtxt

Nuevo Post: https://dev1ls.deno.dev/yggdrasil-la-red-mesh-ipv6-descentralizada #NixOS #ipv6 #yggdrasil #Dev

Nuevos Proyectos, Nueva imagen, nuevo todo! #BCN #logo #Tech #Dev

GTK2 about to be removed from the official Arch repos: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/2BDHYLEFSYQBDTMUOZT5J6AFTA5M3FO6/

It’ll probably all be dropped to the AUR, so I can build this myself, because I still have some stuff that depends on it (and will never receive further updates).

@movq@www.uninformativ.de My impression also is that good sysadmins are missing. No wonder if they all get laid off because they’re “not doing anything” and developers can just operate their shit themselves. Or so the bosses and plenty devs think. Sadly, that’s the general view.

Hell no, devops is bullshit in my opinion. Most developers (including myself) are rather bad at administrating. A good sysadmin offers other skills. Great admins appear to just sit around, but they’re much more proactively working than programmers who also operate the same stuff. The latter have a waaay more reactive work model in comparison. When things have already gone south. The sysadmin, on the other hand, would have noticed and thus prevented the vast majority very early on when it was far from becoming a problem in the future.

At least that’s my personal experience in all those years in different projects and what my mates tell me from their companies. Sure, skills can be learned, but it’s just not happening (enough). And obviously, there are people out there who excel in both disciplines, but they are rare. Most fall in one of the categories. Not to forget, plenty are just bad at everything. :-)

mask : gemi.dev get attack,errors or maintenance!?? huuft.. now can’t open waffle news and chilli weather 😑 mybe must build backup data on other host or do other option to get solutions…

@important_dev_news@n8n.andros.dev Fuxk me decision makers are fuxking stupid sometimes 🤣

Color negro brillante e irresistible.
#catsoftwtxt

@important_dev_news@n8n.andros.dev Thank fuxk 🤣

• ¿Te gusta el nuevo pienso? Es bajo en calorías. -
  #catsoftwtxt

@bender@twtxt.net The first format use the subject extension while the other is a new format that is inspired by mentions format, the first one should be compatible but I’m not sure, if it’s used verbatim by the client it would work, but if we consider the new proposal for it to have an optional part it wont work on clients without changes.

@zvava@twtxt.net Going to have to hard disagree here I’m sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) I’m sorry you’ve completely lost me! I’m old enough to pre-date before Linux became popular, so I’m not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject) whose contents is a cryptographic content-addressable hash of the “thing”™ you’re replying to and forming a chain of other replies (a thread).

I’m sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a “Magic Date” for which our clients use the modified function(s).

@prologic@twtxt.net thanks, I already follow @important_dev_news@n8n.andros.dev too.

BTW, the feed on https://feeds.twtxt.net/ seem down? It says it’s in maintenance.

@bender@twtxt.net https://andros.dev/texudus.txt, its url doesn’t correspond to the feed either

@zvava@twtxt.net @movq@www.uninformativ.de I’m not entirely sure about the spaces, but maybe they were omitted to simplify parsing of mentions in the form of @<nick url>. If the next token after the @<nick does not look like a URL, it’s not a mention but regular text. This is just wild guessing, though.

Looking at the regex and tests in the original twtxt reference implementation seems to confirm that theory in the sense as it relies on whitespace as the delimiter:

Another thing about nicks is that the original twtxt reference implementation converts nicks to all lowercase:

You probably know this already, the original twtxt file format specification can be found here: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html

As for extensions, I don’t know of anything outside of twtxt.dev that has actually been (partially) implemented. However, there is also the issue tracker of the official reference implementation. You might wanna dig through that. For example, there is an alternative suggestions of multiline messages: https://github.com/buckket/twtxt/issues/157

@zvava@twtxt.net Good question. This is the spec, I think:

https://twtxt.dev/exts/metadata.html#nick

It doesn’t say much. 🤔

In the wild, I’ve only seen “traditional” nick names, i.e. ASCII 0x21 thru 0x7E.

My client removes anything but r'[a-zA-Z0-9]' from nick names.

is there consensus on what characters should(n’t) be allowed in nicks? i remember reading somewhere whitespace should not be allowed, but i don’t see it in the spec on twtxt.dev — in fact, are there any other resources on twtxt extensions outside of twtxt.dev?

@thecanine@twtxt.net Id like that too, it just can’t come from me, because native mobile dev just isn’t my thing 😢

@zvava@twtxt.net Herw you go: https://git.mills.io/yarnsocial/twtxt.dev/pulls/28

Dear dev.alessandrocutolo.it, do you really need to fetch my twtxt feed every 20-30 seconds? 😅 Not that it’s posing a problem, but I feel like this could be optimized. For example, how about using the if-modified-since request header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/If-Modified-Since

@important_dev_news@n8n.andros.dev This feels like a decision that punishes Mozilla and Apple, way more than it punishes Google.

@dce@hashnix.club No worries 😌 It’s all documented in our soecs, it’s not such a common thing that we’ve felt the great need to really solve, we’re aware folks want to sometimes have their feed on several protocols, and that’s totally fine™ 😅

@bender@twtxt.net This one: https://n8n.andros.dev/webhook/f0cfd6a6-60c8-4183-a26d-120bbd25a046

Evitando que mi humano trabaje para darme mimitos.
#catsoftwtxt

🚀 BCN #nix #dev #ygg

Soy el detective Baldo. Aún recuerdo cuando esa gatita salvaje entró en mi caja contoneando su cola. Le habían robado el cascabel de oro. Acepté el caso sin dudarlo, quería meter los bigotes en ese caso. Olía a pescado podrido.
#catsoftwtxt

@kat@yarn.girlonthemoon.xyz On the one hand, all these programs have a very long history and the technology behind manpages is actually very powerful – you can use it to write books:

https://www.troff.org/pubs.html

I have two books from that list, for example “The UNIX programming environment”:

It’s a bit older, of course, but it looks and feels like a normal book, and it uses the same tech as manpages – which I think is really cool. 😎

It’s comparable to LaTeX (just harder/different to use) but much faster than LaTeX. You can also do stuff like render manpages as a PDF (man -Tpdf cp >cp.pdf) or as an HTML file (man -Thtml cp >cp.html). I think I once made slides for a talk this way.

On the other hand, traditional manpages (i.e., ones that are not written in mandoc) do not use semantic markup. They literally say, “this text is bold, that text over here is italics”, and so on.

So when you run man foo, it has no other choice but to show it in black, white, bold, underline – showing it in color would be wrong, because that’s not what the source code of that manpage says.

Colorizing them is a hack, to be honest. You’re not meant to do this. (The devs actually broke this by accident recently. They themselves aren’t really aware that people use colors.)

If mandoc and semantic markup was more commonly used, I think it would be easier to convince the devs to add proper customizable colors.

-¡Deja de estudiar y hazme caso!-
#catsoftwtxt

i signed up for omg.lol and i’m really liking it. such a cozy and fun little community with a suite of fun web things. i wish the financial barrier to entry was a bit lower though (maybe like $5 for a few months on it or something) just so i could recommend it to my broke friends more, but i totally get why it’s priced the way it is (solo dev!!!)

In 1996, they came up with the X11 “SECURITY” extension:

https://www.reddit.com/r/linux/comments/4w548u/what_is_up_with_the_x11_security_extension/

This is what could have (eventually) solved the security issues that we’re currently seeing with X11. Those issues are cited as one of the reasons for switching to Wayland.

That extension never took off. The person on reddit wonders why – I think it’s simple: Containers and sandboxes weren’t a thing in 1996. It hardly mattered if X11 was “insecure”. If you could run an X11 client, you probably already had access to the machine and could just do all kinds of other nasty things.

Today, sandboxing is a thing. Today, this matters.

I’ve heard so many times that “X11 is beyond fixable, it’s hopeless.” I don’t believe that. I believe that these problems are solveable with X11 and some devs have said “yeah, we could have kept working on it”. It’s that people don’t want to do it:

Why not extend the X server?

Because for the first time we have a realistic chance of not having to do that.

https://wayland.freedesktop.org/faq.html

I’m not in a position to judge the devs. Maybe the X.Org code really is so bad that you want to run away, screaming in horror. I don’t know.

But all this was a choice. I don’t buy the argument that we never would have gotten rid of things like core fonts.

All the toolkits and programs had to be ported to Wayland. A huge, still unfinished effort. If that was an acceptable thing to do, then it would have been acceptable to make an “X12” that keeps all the good things about X11, remains compatible where feasible, eliminates the problems, and requires some clients to be adjusted. (You could have still made “X11X12” like “XWayland” for actual legacy programs.)