@Sumomo@sumomo.neocities.org You should report the bug and hopefully get it fixed 🤞

@brytboi@twtpub.com I hope you’re seeing my replies because you absolutely can scroll up in the app. Let me know if you’ve run into a bug though and report it to me so I can fix it immediately!

Testinf image upload fixes…

Testing image upload fixes 🙏

@david@daiwei.me Are you able to describe this bug as an Issue in the Gitea Issue Tracker such that it can be reproduced and fixed? 🙏

I hate having my website offline, so I tried to bring it back in a honey-potted version: “AI” agents get served article versions with inverted meaning, like “do” replaced with “don’t” and so on.

It didn’t work. Claude noticed it and “fixed” it back to the original version. When I asked it, “wait, nowhere on the page does it say $string, check again”, it said:

Image

This is the creepiest shit ever. Silently “fixing” stuff behind my back is the epitome of untrustworthiness.

Open the bay doors, HAL.

This has been fixed now if you could retest?

Finally, I added some tests and fixed this. After updating the feed metadata, I now just return early and do not attempt to build an SQL multi-value INSERT statement. Easy-peasy.

@david@daiwei.me This has now been fixed! 🎉

Okay I’m fixing this in lextwt, yarnd and twtxt.app (takes a different path). Soon you’ll be able to write shit™ like (<this>) and it’ll get escaped and rendered correctly on the page. Basically you are really writing HTML here, but not intending to do so, Twtxt never supported HTML, and I don’t think it ever should. We extended the format to support basic Markdown, and I think that’s where it should end.

Probably time we wrote a Spec for this really.

I am sooooooooooooooooooooooooooooooooooooooooooooooooOOOOOOOOOOOOOOoooooooooooooooo tired of “fast-moving” software. ruff changed a ton of stuff and now all my code bases “need fixing”. Blah.

And SemVer is worth nothing if your 4 year old program with over 16’000 commits is still at “version 0.x”. Blah!

Everything is horrible.

Data protection, @dce@hashnix.club! :-D

This revealed another bug in my client that I still need to fix at some point. Inserting an empty set of messages failed with an SQL logic error. Whoops. I didn’t think about that corner case.

@movq@www.uninformativ.de Good question. Tarballs are probably not needed, but might be convenient for people who don’t want to or can use a version control system. Not sure if there are non-techies who use your software. Tarballs for branches are overkill, though, I agree.

Looking at this more closely: As for the feeds, how about filenames “tags.atom” and “commits.atom”? Unless, of course, they were already named like that before.

For the tags feed it would be cool to include the actual changelog entries to be more useful if somebody takes this approach to get notified of new versions. But that would mean you have to duplicate the changelog entry into the annotated tag. And then you can’t fix changelog typos in the feed anymore. Alternatively, the feed generation would need to extract the section from the the CHANGES file. That has the benefit of automatically providing changelogs for past versions in the feed.

Ahh yes! Please do upgrade your twtd instance. Few things changed, many bugs fixed there too.

the correct fix for what you observed is a recovery token to re-sync settings from the sync API

I should really fix this damn bug where new replies to read replies to unknown conversation roots are not showing up in tt. I run into this bug almost daily for weeks now.

@dce@hashnix.club Fixed! 🥳 That 403 was our bug — connect was checking your token via /api/v1/user (needs read:user), but your token’s scoped to just the repo so it can’t. Now it validates against the repo itself instead 👍

@david@daiwei.me I think it might be a bug i just fixed 🤞

@dce@hashnix.club Ahh! Let’s fix the 403 error then? I don’t have access to Codeberg, so I can’t reasily test. Can you walk me through what you tried and any other details? I’ll get this fixed.

@david@daiwei.me Found it. Some bugs in the “claim limiter”. Fixing…

@prologic@twtxt.net @david@daiwei.me Thanks! Hahaha, rest assured, it was not right from the beginning at all. I had to fix it over and over again.

@david@collantes.us heads up 👋 that verification code never reached you — outbound email was broken on my end (my mail relay was rejecting twtxt.net senders 🤦‍♂️). Fixed + deployed now 🥳 give the hosted feed another go, it’ll land this time 🤞

@david@daiwei.me It’s all fixed now, for good 😌

Shipped a bunch of Twtxt App fixes & polish today 🥳 One-tap Refresh that actually refreshes, duplicate follows fixed, Reply/Fork buttons (with proper @-mentions), unread dots, Back keeps your spot, and it’ll now guide you to install it as a proper app 📱 Reload https://twtxt.app and have a play! Thanks @quark@ferengi.one and @balloon-fu-sen@tw.fus.f5.si for all the reports 🙏

@david@daiwei.me Ah, edits. Okay. Let’s hope that it’s all fixed then. 🤞

@david@daiwei.me Exactly. Spaces are fixed, tabs always break the layout when the tab sizes are different.

@balloon-fu-sen@tw.fus.f5.si Fixed! 🥳 The Avatar URL field now actually gets written to your feed’s # avatar = metadata. Turned out it needed changes in both the app and twtd itself — so you’ll want to update your twtd instance once the new build lands. Thanks for the report! 🙏

@balloon-fu-sen@tw.fus.f5.si Ahhh! That’s a bug! Lemme fix that!

🥳 Finally! After nearly 4 years, yarnd v0.16.0 “Silver Sojourner” is out! 🚀 Twt Hash v2, SQLite FTS5 search, HTMX-powered UI, first-time setup wizard and literally hundreds of bug fixes 🐛

Release notes: https://git.mills.io/yarnsocial/yarn/releases/tag/0.16.0

Upgrading is fully automatic — the Twt Hash v2 migration re-fetches all feeds on first start, so expect the first cycle to be a bit heavier. Images on Docker Hub as prologic/yarnd:0.16.0 👌

cc @kat@yarn.girlonthemoon.xyz @abucci@anthony.buc.ci @shinyoukai@yume.laidback.moe @eldersnake@we.loveprivacy.club 🙏

Yeah to @david@daiwei.me’s point re Editing. It’s only really safe to do so if you are sure that no-one has yet fetched your feed or replied to your Twt. But even then, you have to be quick 🤣 Editing/fixing a Twt inside of an existing thread is “oaky”, as long as it also doesn’t get forked and becomes the root of a new conversation 😅

@bender@twtxt.net Yeah, Yarnd’s mention parser is pretty naive — if twtxt.app wraps the mention in quotes it probably strips them wrong. Worth fixing 🤔

@bender@twtxt.net No idea. I can only tell you that the correct hash would have been rwzz277nkyju for this line:

[2026-07-11 14:47:17+00:00] [(#5bpwpdcjnhcz) <a href="https://txt.sour.is/external?uri=https://daiwei.me/twtxt.txt">@david<em>@daiwei.me</em></a> (This thread is broken again on my end. Another bug or fix not released yet? 😅)]

@david@daiwei.me (This thread is broken again on my end. Another bug or fix not released yet? 😅)

Fixed the broken hashes in the Twtxt App (https://twtxt.app) 🥳 It was hashing your twts with a client-side timestamp the server never used 🤦‍♂️ Now it keeps the canonical created/hash the pod (or twtd) returns, and the GitHub/Gitea backends write a # url = preamble so every client hashes your feed the same way. Thanks @fastidious@tilde.town for the report 🙏

I will aim to have most issues bugs and user experience problems, identified and fixed by this weekend!

@aelaraji@aelaraji.com do not use twtxt.app yet. It has issues that @prologic@twtxt.net will fix soon.

I don’t know why, but either Jenny’s behaving different after the last update, or I Fucked up something and I have no Idea how to fix it.

Symptoms:

• I don’t have copies of my New Posts in my Maildir after posting them (as in I don’t see them in neomutt’s inbox).
  
• Nor fetch or fetch context (if they get replied to) seem to fech them auto-magically.
  
• I had to do a full whipe (~/Maildir/twtxt and ~/.cache/jenny) in order to get them fetched back.

Fixed! Had to unfollow, follow back.

@prologic@twtxt.net My bad. It has been a while since the last time I poked around my mystery box, and I must have Effed up something yesterday. Is it fixed now? (Also, I’ve noticed that access to my avatar is, somehow, still denied. Still poking at it. 🤦)

@GabesArcade@gabesarcade.com Thanks for reporting! I will fix this 👌 Soon!

@bender@twtxt.net Haha! Thanks. The broken avatar was a Me and my Hotlinking policy problem, It should be fixed by now. And I Freaking love the twtxt.app by the way. Cheers!

FYi 👋 I’m aware of an optimist precomputed hashing bug on the new twtxt.app 🤯 Trying to work with @bender@twtxt.net remotely on my vacation yo fix it 🤣

Fixed 👌

I think I fixed this bug!

@lyse@lyse.isobeef.org Found it and fixed it! 🎉 The crawler’s discovery spider was fetching every feed a second time, without any conditional headers (plus a couple of other politeness bugs: redirected feed URLs never stored their cache validators, and there was no floor between re-fetches). Now every feed is fetched at most once per crawl, always with If-Modified-Since / If-None-Match, and never more than once per 15m no matter what. Just deployed — please keep an eye on your access logs and let me know if you still see anything impolite from the crawler 🙏

@lyse@lyse.isobeef.org I believe this is fixed now 🤞

Ahh yes, you really must fix your nick haha 🤣

@movq@www.uninformativ.de It was an easy and quick fix, though. :-)

@movq@www.uninformativ.de Yes, that’s what I was thinking, too. For a moment, I wanted to suggest to use <ol> instead of <ul> to fix that. However, that’s only gonna work for the first level, but subsections then miss their parent level.

And it turns out that I was wrong. At least sort of. There are some CSS tricks to fix it: https://stackoverflow.com/a/26243681 Of course, with text or retro browsers, this is not gonna fly.

I also came across this interesting article. I just skimmed it and it’s about real tables of contents with page numbers, so not what you have in mind, but cool nevertheless: https://css-tricks.com/a-perfect-table-of-contents-with-html-css/

I complain about this a lot:

https://movq.de/v/e7cb49eefb/hiccupfx

But to be honest, my blog did the same thing – to some degree.

This is fixed now. The trick is to add width and height to all <img> tags. That way, modern browsers know how much space to reserve for the image. Without this, they just reserve zero space, so when the image finally loads, you get jumpy layout.

This effect is even worse when you use <img loading="lazy"> – which I can finally use, now that the jumpy layout has been fixed. 🥳

@movq@www.uninformativ.de I reckon section numbers are not really needed for articles. But if you number them, the anchors should probably not contain the section number, just the title. Especially for articles that may receive updates.

It’s probably another story for specifications. They’re kinda fixed and thus I found it useful in the past to include the section numbers in the anchors, so they show up in URLs when linking to specific sections. W3C RFCs only include the numbering in the anchors. This makes URLs fairly short, but it would be also nice to directly see what kind of section that URL actually links to.

@movq@www.uninformativ.de Yeah, the damn message to urge me into updating for no reason. It still works fine, why update then!? Leave me alone. If downloading fails, there’s already a hint that updating might fix it. The introduction of this banner in https://github.com/yt-dlp/yt-dlp/pull/13937 doesn’t give any reason for that change either.

@lyse@lyse.isobeef.org Interesting approach. 🤔

The master branch should never be in a broken state (apart from bugs I don’t know about). Any intermediate state during the development of a larger feature will happen in a different branch.

I mean, yeah, but … I don’t know, I like having “traditional releases” as a second safety net when I write programs. I like to let things mature for a while and then I cut a new release. So it’s, like, “we have a bunch of new features and fixes here, and to the best of my knowledge this works fine now”. But maybe I’m just paranoid. 🤔

Getting the vim key bindings to work for focus switching in this modal dialog took me forever. Only cursors and (Shift+)Tab are supported out of the box. I absolutely understand that, it’s fine. I installed an input handler on the dialog, but the focus always stayed the same.

After two wasted hours, I was in despair to copy the tview.Modal into my own code base. Of course, I had to fix all the private tview field accesses first. But even installing the input handler directly on the buttons themselves did not work. Even though, the handler was definitely executed, the focus did not shift. Forcing redraws as a last resort also did not work.

Looking through all the messy chained input handling, I eventually stumbled across another place in the tview.Form, which is internally used by tview.Modal. This messed around with app focus receptions and input handlers. This gave me the idea to make the tview.Application refocus my modal dialog after I told the modal dialog which button to select. And would you look at that, this did the trick! I haven’t completely figured out what is going on exactly, but I could get rid of my Modal clone again.

I always go through hell with focus handling in tview. Each and every time. It just does not feel natural to me. Complete brainfuck to wrap my head around. The Urwid API felt sooo much more refined, it never was an issue. It just works. In fact, I cannot think of any other TUI library that has remotely the same pain level when it comes to focusing widgets as tview.

Now I’m curious how movwin deals with that. ;-)

Every now and then, I think that I have carefully proof-read my message enough times and hit the “Add message” button in tt. But then, in the message tree, I spot another missed typo. My process is then to go to my twtxt.txt and fix it by hand. However, I still have to clean up tt’s cache. This is rather tidious:

1. Recall the sqlitebrowser ~/.local/share/twtxt/tt2.sqlite from my shell history.
   
2. Switch to the “Browse data” tab.
   
3. Go to the messages table and wait a second or two until it’s loaded.
   
4. Sort by the created_at column twice, so that I get descending order.
   
5. Select the first message, which is typically the one in question.
   
6. Find the “Remove currently selected row” button in the tool bar.
   
7. Commit the changes.
   
8. Close sqlitebrowser.
   

So, I finally implemented the removal of messages from the cache in tt. I can now hit d and confirm the removal. Bam! Should have done that ages ago!

Image

Next up is the search, I think.

I just fixed it.

A man kept asking his flatmate on dates. Talika’s idea might fix the problem
Years of soaring property prices have meant the age of renters extend well beyond young adults and into new generations. But for women, it can come with additional hurdles. ⌘ Read more

Nobody ever gets credit for fixing problems that never happened (2002) [pdf]
Article URL: https://web.mit.edu/nelsonr/www/Repenning=Sterman_CMR_su01_.pdf

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

Points: 3

# Comments: 0 ⌘ Read more

When my git history is just “fix”, “actually fix”, “this time for real” and “pleasepleaseplease” ⌘ Read more

CISA Tells US Agencies to Fix Security Bugs in as Little as 3 Days Thanks to AI Threats
“Defenders cannot afford to take weeks to patch,” one Cybersecurity and Infrastructure Security Agency official warned on Wednesday. ⌘ Read more

@lyse@lyse.isobeef.org Yeah, it probably would look better. I might fix that. It’s just laziness, the implementation was easier this way. 😅

Glad you find it interesting! And honestly, I agree, nobody but me would use this anyway. There are more mature and featureful toolkits out there.

When the ticket just says “fix the issue” and nothing else ⌘ Read more

@itsericwoodward@itsericwoodward.com Turns out, this is a bug in my config to cache synchronization. Nickname changes in the configuration file are just not synced to the cache at startup if the feed URL already exists in the cache. I must have fixed this typo in my config ages ago, because I don’t even recall having that spelling mistake to begin with. Yet, the cache was happily showing the erroneous nickname. Composing a reply automatically adds the mentions from the conversation participants. Everything originates from the cache, so, I successfully poissoned my replies.

@itsericwoodward@itsericwoodward.com That DORA quote is 🤯 — and it perfectly explains why AI coding tools terrify me in certain contexts. Dropping Copilot into a codebase full of technical debt isn’t gonna fix the debt, it’s just gonna write more of it faster 🤣 Fred Brooks would be nodding his head right now 🙏

To fix housing, we must try something radical. Here are three ideas to shift the dial
Australia already has more homes than households. It’s just that too many of our homes cannot house the people who need them. ⌘ Read more

Astronauts on ISS told to shelter as repairs under way to fix air leaks
Article URL: https://www.bbc.com/news/live/c4g44ew3g1kt

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

Points: 13

# Comments: 2 ⌘ Read more

Ask HN: Is the web for machines (/llm.txt) the one we wished we had as humans?
I got really tired, as a human, of parsing the standard marketing heavy web we have today.
I’ve always loved the simplicity of gopher and gemini web.

Recently I found myself manually adding `/llm.txt` to most websites I visit because I find the content for LLMs strait to the point and clear.
The only annoyance is web browsers like chrome do not render the markdown.

So could the AI revolution actually fix the web for humans as a side effect? … ⌘ Read more

‘Had an absolute crack’: Top player in Big Build clean-up steps down
Top official Steve Dargarvel has been regarded as one of the most effective players in attempting to fix Victoria’s scandal-ridden construction sector. ⌘ Read more

Data Center Operators Are Trying to Fix Their Water Use Problems
Google, Microsoft, and other hyperscalers have come under scrutiny for their impact on water quality and availability. ⌘ Read more

@movq@www.uninformativ.de It’s the “Lyse types the entire HTML by hand” generator. Yes, no kidding. I write articles so rarely, that I can do that once in a while. It’s fun to some degree, but also not.

After some time, I finally recorded some Vim macros to insert <b>…</b>, <var>…</var>, <span class=s>…</span> etc. around the tokens. This helped a little bit. But I was still questioning my mental state doing it like that. I also had to fix a bunch of the end tags by hand, because the word movement wasn’t enough or the end movement went too far. Quite the annoying process for sure.

But I think the HTML looks a wee bit nicer and is maybe even semantically a little bit better than having only <span>s everywhere. I find the <span class="whatever"> just soo awfully long. Of course, I never look at the code again, but knowing, that e.g. there is a <b> and it saves so many bytes in comparison, makes me happy. It is a more elegant solution in my opinion. Not by much, but better nonetheless. It’s a matter of simplicity. Admittedly, even I can’t avoid the <span>s alltogether. Oh well. On the other hand, I’m sure that this does not make any difference whatsoever. I bet, nobody and nothing, like a screenreader, analyzes the HTML for that, where this would be truly useful.

Oh! Maybe text browsers, though. It just occurred to me while composing this reply. :-) Haha, I lost my bet quickly. w3m picks up at least the <b> for keywords and builtin types, <u> for filenames and <i> for comments. Yey. No different styles for <var> and <mark>, unfortunately. elinks only renders the bold. It’s cool that I had the right intuition right from the beginning, despite being unable to pinpoint it. :-)

All the <span> hell with common syntax highlighters is a downer for me that keeps me from looking more into them. If I wrote more articles, I might rig something up with Pygments. At least that’s somehow positively connotated in my brain. Not sure if it actually deserves it, but I dealt with that in some loose form (can’t even remember) years and years ago. Apparently, it wasn’t too terrible.

To prepare the table of contents, I used grep and sed with some manual intervention in the end. The entire process can be improved. Absolutely.

You wrote your own site generator, didn’t you?

Labor, Coalition to avoid repaying investment funds under donations fix
The major parties would dodge paying back donations from their investment funds if they have already spent the cash, under the government’s plan to restore campaign finance laws. ⌘ Read more

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

‘They’re laughing at us’: How a community lost its beloved bowlo
Norths Leagues Club promised to fix the Bangalow Bowlo’s dilapidated clubhouse when they went into partnership. Now it’s using the state of the clubhouse to justify its decision to close the club. ⌘ Read more

‘They’re laughing at us’: How a community lost its beloved bowlo
Norths Leagues Club promised to fix the Bangalow Bowlo’s dilapidated clubhouse when they went into partnership. Now it’s using the state of the clubhouse to justify its decision to close the club. ⌘ Read more

‘They’re laughing at us’: How a community lost its beloved bowlo
Norths Leagues Club promised to fix the Bangalow Bowlo’s dilapidated clubhouse when they went into partnership. Now it’s using the state of the clubhouse to justify its decision to close the club. ⌘ Read more

Oh boy, it was bloody humid this morning. Just around 20°C when we left, but climbing rapidly. The flow of air when walking was okay, but as soon as we stopped, streams of sweat were pouring down on us. Luckily, it was cloudy, but the lack of wind was bad. Now, the sun is out, 29°C will be reached in an hour and I’m glad that the house is still cool. It will be a different story in a few weeks or months. Not looking forward to that at ll.

On the bright side, we saw the first tadpoles of the year and an also first, but sadly dead slow worm that probably some bird dropped on a bench next to the fountain. The fly was stuck to its feast and also cactus. The municipality fixed the railing nicely and we came across a giant patch of great looking fire bugs on the summit.

All in all, a successful stroll through the woods but for the humid heat.

https://lyse.isobeef.org/waldspaziergang-2026-05-30/

Long famed for its food, this Sydney suburb is about to get a nightlife boost
Sydneysiders are increasingly looking beyond the CBD for a nightlife fix – and Eastwood is the next go-to. ⌘ Read more

The Pentagon Knew Enemies Could Track Troops’ Phones for Years. Now They Are
The US military has long known that cheap fixes could stop location data from exposing its troops. It adopted almost none—and now says adversaries are using the data to target soldiers during a war. ⌘ Read more

@bender@twtxt.net If you break it, I will fix it 😅

Can OpenAI’s ‘Master of Disaster’ Fix AI’s Reputation Crisis?
Global affairs chief Chris Lehane wants to tone down the debate over AI’s societal impacts—and get states to pass laws that won’t derail OpenAI’s meteoric rise. ⌘ Read more

When I find an old comment in my code: “fix found on Stack Overflow” ⌘ Read more

When I ask Claude Code to fix a bug but forgot to give it access to my repo ⌘ Read more

Our storage box is not reachable for hours, the support response is unhelpful to say the least. Let’s see how long it takes them to actually fix this. Until then, no photo galleries etc. available.

How I Fixed My Webcam Lighting for Zoom Calls (2026)
I have a horrendous lighting setup in my home office, but as a mixed-use room, my options for fixing it were limited. ⌘ Read more

How I Fixed My Webcam Lighting for Zoom Calls (2026)
I have a horrendous lighting setup in my home office, but as a mixed-use room, my options for fixing it were limited. ⌘ Read more

@lyse@lyse.isobeef.org yes, yarnd has a few parser (?) issues that were never resolved. If only a powerful token predictor could fix it, once and for all… 😅

Colorado’s Anti-Repair Bill Is Dead
Colorado has led the US on legislation that ensures people can fix their stuff. Manufacturers tried to claw back that control, but ultimately failed—for now. ⌘ Read more

When I fixed a coworker’s code but lost 2 hours helping them ⌘ Read more

When the lead dev personally goes to the client to fix a major bug ⌘ Read more

When it’s the sixth time ChatGPT fails to fix the same bug ⌘ Read more

When I finally manage to fix a bug after pulling an all-nighter ⌘ Read more

When someone comes looking for me to fix a bug in production ⌘ Read more

When the intern fixes in 15 minutes the bug I’ve been stuck on all day ⌘ Read more

@lyse@lyse.isobeef.org Oops, I guess the new text is a bit obscure. If you follow the link, the text is a bit more explicit, but you still need to know what a lexical scope is. Anyway, this is part of Perl moving very carefully toward being UTF-8 by default while also not breaking code written in the 90s. If you name a recent version like “use v5.42;” then Perl stops letting you use non-ASCII characters unless you also say “use utf8;”. The “lexically” part basically means that strictness continues until the next “}”, or the end of the program. That lets you fix up old code one block at a time, if you aren’t ready to apply the new strictness to a whole file at once.

Artemis II technical issues fixed: NASA reveals new launch date
It looks like mankind’s first trip around the Moon in decades may finally be happening in the very near future. For those hoping to bear witness to th… ⌘ Read more

When I manage to fix the bug the team had been stuck on for days ⌘ Read more

When I manage to fix a bug without using Google or an AI ⌘ Read more

When I keep chaining fixes to solve the same bug ⌘ Read more

When we deploy fixes to prod without having tested them ⌘ Read more

When a coworker mass-commits 47 files with the single message “fix” ⌘ Read more