@alexonit@twtxt.alessandrocutolo.it Hahaha, that made me laugh real good. :-D I find it always surprising what collects in a short amount of time.

@zvava@twtxt.net Yes, the specification defines the first url to be used for hashing. No matter if it points to a different feed or whatever. Just unsubscribe from malicious feeds and you’re done.

Since the first url is used for hashing, it must never change. Otherwise, it will break threading, as you already noticed. If your feed moves and you wanna keep the old messages in the same new feed, you still have to point to the old url location and keep that forever. But you can add more urls. As I said several times in the past, in hindsight, using the first url was a big mistake. It would have been much better, if the last encountered url were used for hashing onwards. This way, feed moves would be relatively straightforward. However, that ship has sailed. Luckily, feeds typically don’t relocate.

10 Bizarre Cases of Killer Seniors
They say murder is a young person’s game. Think again. Court records are full of murderous Methuselahs, senile slashers, and wrinkled reapers. Sometimes they kill out of mental illness; other times, dementia. Some become violent after strokes. Others may be scam victims fighting for survival. A few start early and evade detection well into their […]

The post [10 Bizarre Cases of Killer Seniors](https://listverse.com/2025/10/01/10-bizarre-cases-of-killer-seniors/ … ⌘ Read more

Measure Twice, Cut Once
⌘ Read more

Measure Twice, Cut Once
⌘ Read more

Winemaking music lover to focus on health after blood cancer diagnosis
WA vigneron Rob Wignall, who built a legacy of award-winning Great Southern wines and star-studded music festivals, says it is time to move on. ⌘ Read more

My September ‘25 in Review
The month of September is now over, too. Only 86 days left until Christmas and 92 days until the New Year. So, it’s time to take a (this time, really) quick look back at the past weeks. ⌘ Read more

Comprehension debt: A ticking time bomb of LLM-generated code
Article URL: https://codemanship.wordpress.com/2025/09/30/comprehension-debt-the-ticking-time-bomb-of-llm-generated-code/

Comments URL: https://news.ycombinator.com/item?id=45423917

Points: 530

# Comments: 334 ⌘ Read more

Why was Windows 3.0’s WinHelp called an online help system when it ran offline?
Some time ago, I described Windows 3.0’s WinHelp as “a program for browsing online help files.” But Windows 3.0 predated the Internet, and these help files were available even if the computer was not connected to any other network. How can it be “online”? ↫ Raymond Chen at The Old New Thing I doubt this will be a conceptual problem for many people reading OSNews, but I can de … ⌘ Read more

time to consoom more based vim tips and tricks ⌘ Read more

For a very first attempt, I’m extremely happy how this tray turned out: https://lyse.isobeef.org/tmp/blechschachtel/ The photos look rougher than in person. The 0.5mm aluminium sheet was 300x200mm to begin with. Now, the accidental outside dimensions are 210x110mm. It took me about an hour to make. Tomorrow, I gotta build a simple folder, so I don’t have to hammer it anymore, but can simply bend it a little at a time.

@movq@www.uninformativ.de You didn’t miss anything. Just time for more useful stuff. ;-)

@prologic@twtxt.net you doing this reminded me of mkws, and Adi. Good times, we have seeing so many people come and go. It is kind of sad, when I think about “jjl”, and Phil, and the many others…

I am feeling “mushy” today. Ugh, ageing sucks.

@prologic@twtxt.net yup, that’s what I meant. The lack of it on the URL is fine, but on the post itself it is always a good idea. Time frames matter.

@prologic@twtxt.net I can’t upload a screenshot (tried, but Yarnd simple “ate” my reply). See https://zsblog.mills.io/posts/hello-zs-blog.html. Is has no date/time on it.

@prologic@twtxt.net They have not rolled it out (yet), they are “just” discussing it (for the n-th time).

@alexonit@twtxt.alessandrocutolo.it Yeah I think we’re overstating the UNIX principles a bit here 🤣 I get what you’re trying to say though @zvava@twtxt.net 😅 If I could go back in time and do it all over again, I would have gotten the Hash length correct and I would have used SHA-256 instead. But someone way smarter than me designed the Twt Hash spec, we adopted it and well here we are today, it works™ 😅

And I need to make something absolutely clear as well here. Twtxt was completely and utterly dead back in {Aug 2020](https://yarn.social/about.html) when I came across the spec and its simplicity and realised the lost opportunity. Since then we’ve continued to grow a small but thriving community. The extensions we’ve built over time have stood and lasted the test of time for the past ~5 years. We need not break things too badly, because what we have today and was designed years ago actually works quite well™ (despite some flaws).

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

@bender@twtxt.net Well honestly, this is just it. My strong position on this is quite simple:

Do the simplest thing that could work.

It’s one of the age old UNIX philosphies.

Therefore, the simplest thing™ to do here is to just increase the hash length, mark a magic™ date/time as @lyse@lyse.isobeef.org has indicated and call it a day. We’ll then be fine for a few hundred years, at which point there’ll be no-one left alive to give a shit™ anyway 🤣

@prologic@twtxt.net considering other alternatives we have seeing (of which I have lost track already), yes. Why don’t you guys (client makers) take a step at a time and, for now, increase the hash length to deal with the collisions. Then location-based addressing can be added… or not, you know. 😅

@lyse@lyse.isobeef.org I can’t remember the last time I came across a 360° video. 🤔

10 Reasons We’ll Always Need Superman
From very early after Superman’s creation, he was considered to be futuristic. In fact, at the time of New York’s 1939 World’s Fair, Superman was called the “Man of Tomorrow.” In many ways, Superman represents the best of humanity: what we aspire to become one day. That is why he resonates with so many people […]

The post 10 Reasons We’ll Always Need Superman appeared first on [Listve … ⌘ Read more

Thanks @bender@twtxt.net it’s been a long time indeed but, I was here the whole time. Just silent. I just didn’t have much meaningful/worth twting about … /ME flips a bird to life

@bender@twtxt.net Thanks for asking!

So, I’ve been working on 2 main twtxt-related projects.

The first is small Node / express application that serves up a twtxt file while allowing its owner to add twts to it (or edit it outright), and I’ve been testing it on my site since the night I made that post. It’s still very much an MVP, and I’ve been intermittently adding features, improving security, and streamlining the code, with an eye to release it after I get an MVP done of project #2 (the reader).

But that’s where I’ve been struggling. The idea seems simple enough - another Node / express app (this one with a Vite-powered front-end) that reads a public twtxt file, parses the “follow” list, grabs (and parses) those twtxt files, and then creates a river of twts out of the result. The pieces work fine in seclusion (and with dummy data), but I keep running into weird issues when reading real-live twtxt files, so some twts come through, while others get lost in the ether. I’ll figure it out eventually, but for now, I’ve been spending far more time than I anticipated just trying to get it to work end-to-end.

On top of it, the 2 projects wound up turning into 4 (so far), as I’ve been spinning out little libraries to use across both apps (like https://jsr.io/@itsericwoodward/fluent-dom-esm, and a forthcoming twtxt helper library).

In the end, I’m hoping to have project 1 (the editor) into beta by the end of October, and project 2 (the reader) into beta sometime after that, but we’ll see.

I hope this has satisfied your curiosity, but if you’d like to know more, please reach out!

💩 on Company Time ⌘ Read more

@aelaraji@aelaraji.com welcome back dude! Long time no see!

@movq@www.uninformativ.de Yeah, it took quite some time to load. But then it was briefly back. Now it’s 503ing immediately all the time.

@prologic@twtxt.net I know we won’t ever convince each other of the other’s favorite addressing scheme. :-D But I wanna address (haha) your concerns:

1. I don’t see any difference between the two schemes regarding link rot and migration. If the URL changes, both approaches are equally terrible as the feed URL is part of the hashed value and reference of some sort in the location-based scheme. It doesn’t matter.

2. The same is true for duplication and forks. Even today, the “cannonical URL” has to be chosen to build the hash. That’s exactly the same with location-based addressing. Why would a mirror only duplicate stuff with location- but not content-based addressing? I really fail to see that. Also, who is using mirrors or relays anyway? I don’t know of any such software to be honest.

3. If there is a spam feed, I just unfollow it. Done. Not a concern for me at all. Not the slightest bit. And the byte verification is THE source of all broken threads when the conversation start is edited. Yes, this can be viewed as a feature, but how many times was it actually a feature and not more behaving as an anti-feature in terms of user experience?

4. I don’t get your argument. If the feed in question is offline, one can simply look in local caches and see if there is a message at that particular time, just like looking up a hash. Where’s the difference? Except that the lookup key is longer or compound or whatever depending on the cache format.

5. Even a new hashing algorithm requires work on clients etc. It’s not that you get some backwards-compatibility for free. It just cannot be backwards-compatible in my opinion, no matter which approach we take. That’s why I believe some magic time for the switch causes the least amount of trouble. You leave the old world untouched and working.

If these are general concerns, I’m completely with you. But I don’t think that they only apply to location-based addressing. That’s how I interpreted your message. I could be wrong. Happy to read your explanations. :-)

Why Apple’s new phone is eSIM only, and what it means for you
Apple executives on why the time is right to break away from the little plastic squares we carry over from phone to phone. ⌘ Read more

@prologic@twtxt.net ah, I was wondering! Hoping you are having a good time, mate! Christening the new RV? :-)

For what I can gather, kind of a waste of time, not a good solution. I might be missing bits, or may haven’t grasp the entire “story”.

Ignite Realtime Blog: Openfire 5.0.2 release!
The IgniteRealtime community is happy to announce a new release of its open source, real-time communications server server Openfire! Version 5.0.2 brings a number of stability improvements and bug fixes.

Notably, it addresses a recently identified security vulnerability, identifies as CVE-2025-59154. The issue allows for potential identity spoofing via unsafe Common Nam … ⌘ Read more

** Standing only **
I tried to sit at my standing desk today for the first time in an eternity. My ability to focus on any task immediately went from pretty fucking solid to“oooh, what if stare into the middle distance?” so I guess I’ll be continuing to exclusively stand at my desk for the next 10 years. ⌘ Read more

XMPP Interop Testing: Lots More Options
Since the last update, we’ve added a lot more options on how to run your tests. We’ve added a slew of new CI systems, this time focussing on freedom-respecting, open source CI systems for your open source projects.

Recent additions include Jenkins, Drone, Harness and Woodpecker.

This brings our total number of CI systems in which you can run XMPP interop tests up to a whopping ELEVEN, plus anywhere else you can run containers!

Whether you’re building … ⌘ Read more

@zvava@twtxt.net For the time being, just show both.

@kat@yarn.girlonthemoon.xyz nope, not normal. Something birdy (because why to use fishy all the time?!) is going on.

@zvava@twtxt.net it is amazing how much you have accomplished in such a short time. Take time to sleep, though! :-)

It was nice to start a walk in the woods with sunshine. The last times it was all soupy. It was quite windy, autumn is certainly here. Soon, the leaves will begin to turn. https://lyse.isobeef.org/waldspaziergang-2025-09-11/

Why now might be a good time to upgrade your iPhone
The lineup for 2026 includes an improved iPhone 17 and 17 Pro, plus the skinny iPhone Air, and phones are not likely to go down in price by this time next year. ⌘ Read more

Oops, maybe I should have posted a reminder. 🥴

@dce@hashnix.club By the time you posted your twt, the red phase was already over. 🙈 Stellarium has a pretty good simulation of the whole thing.

Winemaker shares devastation after lithium battery fire guts warehouse
A long-time winemaker says he opened his door to explosions and a black ball of smoke as a fire caused by a cordless screwdriver destroyed a lifetime collection of tools and machinery. ⌘ Read more

Three weather services with three different forecasts. We got a little bit rained on, so at least some of them were not completely wrong. The timing was off by an hour, though. And nobody expected the Spanish inqui^W^Wthunder either. It was a nice walk.

Oh cool, as I type this, lighning and thunder very close by now. At most a kilometer away. Glad I’m home and not in the woods anymore. And heavy rain kicks in, too.

@lyse@lyse.isobeef.org (Haha, every time I read the word “Gophers”, I have to stop and remind myself that this is about Golang. 🤪)

@lyse@lyse.isobeef.org I usually only have my GPS tracker with me. That trip yesterday was probably a one-time thing. 😅 It was fun, but I’d rather not carry so much stuff around. 🥴

@dce@hashnix.club Glad you liked it. 😅

@movq@www.uninformativ.de Oh, nice read!

If I’m in the woods, I’d like to not waste my time with computers and focus on the beauty of nature. ;-) So, I’m not gonna participate in that event. But I’d read your articles on that subject anytime. :-)

@lyse@lyse.isobeef.org Or, the time of year when birds take to the skies in stunning flocks.🦆🦢

Looks like it’s this time of the year again where we get beautiful sunsets more often: https://lyse.isobeef.org/abendhimmel-2025-09-01/

Ni Hao; bīng qílín!
I’m just dropping in, to emphasize my love for ice cream and the Chinese crawler bots, allocating their time and resources, towards scraping my humble website.

To show my gratitude, I’ve even added a random little dog generator to https://thecanine.ueuo.com/sparkle.html so that everyone can pick up their own custom dogFT, on their journey through my site.

Now that’s interesting. Some of these bots start crawling at URLs like this:

https://uninformativ.de/projects/lariza/NetTracer-Scenes/GPUTracer/multipass/xlonitor/http-collect/getpw

That is obviously completely wrong. But I can explain it. Some years ago, I screwed up my nginx rewrite rules, and that’s how these broken URLs came to be.

It all redirects to /git now, which is why that endpoint sees so much traffic lately.

But what does that mean? Why do they start there? I can only speculate that this company bought an old database of web links and they use that to start crawling. And it was probably a cheap one, because these redirects have been fixed for quite a long time now.