@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.
D7VK 2.0 released with more performance fixes for retro Direct3D games on Linux
Love your classic retro games? D7VK 2.0 is out now to bring more performance improvements for running retro Direct3D games on Linux.
Read the full article on [GamingOnLinux](https://www.gamingonlinux.com/2026/07/d7vk-2-0-released-with-more-performance-fixes-for-retro-direct3d-ga … ⌘ Read more
DXVK 3.0.2 brings bug fixes for Dying Light: The Beast, Halo and more on Linux / SteamOS
Direct 3D 8, 9, 10 and 11 to Vulkan layer DXVK has a new bug fix release out, sorting some issues in specific games to make gaming on Linux / SteamOS better.
Read the full article on [GamingOnLinux](https://www.gamingonlinux.com/2026/07/dxvk-3-0-2-brings-bug-fixes-for-dying-light-the … ⌘ Read more
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 🤞
Proton Experimental brings fixes for Diablo IV, Marvel Rivals, RPGMaker Engine games
Valve launched the latest update to Proton Experimental to bring more fixes for running Windows games on SteamOS / Linux including Steam Deck and Steam Machine.
Read the full article on [GamingOnLinux](https://www.gamingonlinux.com/2026/07/proton-experimental-brings-fixes … ⌘ Read more
@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.
twtxt.net senders 🤦♂️). Fixed + deployed now 🥳 give the hosted feed another go, it'll land this time 🤞
@david@daiwei.me Found it. Some bugs in the “claim limiter”. Fixing…
gg instead of g to go to the top in tt. Much better! :-) Other multi-key combinations are also easily possible now.
@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://we.loveprivacy.club/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 👌
lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🤣
I think I fixed this bug!
OpenRazer 3.12.4 Fixes Compatibility With Linux 7.2
OpenRazer 3.12.4 is now available as the newest update to these out-of-tree, unofficial Linux drivers for Razer devices. OpenRazer when paired with the likes of Polychromatic or other GUI options is what makes for a nice experience running Razer gaming peripherals under Linux… ⌘ Read more
@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 🙏
KWin Compositor In KDE Plasma 6.8 Drops Support For Desktop OpenGL
Along with releasing Plasma 6.7.2 this week, KDE developers continue to be quite busy working on new features and improvements for the Plasma 6.8 release while also furthering along fixes for future Plasma 6.7 point releases… ⌘ Read more
@lyse@lyse.isobeef.org I believe this is fixed now 🤞
Ahh yes, you really must fix your nick haha 🤣
UPower 1.91.3 Fixes Behavior To Avoid Degrading Your Laptop Battery Faster
The UPower abstraction layer used for power management on Linux systems, especially laptops and desktops, is out with an important fix today to avoid inadvertently falling back to the laptop battery “fast” charging mode on some laptops that in turn could degrade your laptop battery faster… ⌘ Read more
@movq@www.uninformativ.de It was an easy and quick fix, though. :-)
COSMIC Epoch 1.2 Desktop Fixes Flickering Issues For Intel Graphics
Just a week after the COSMIC Epoch 1.1 release with its slick new system monitor, COSMIC Epoch 1.2 is now available for this Rust-based desktop developed by System76… ⌘ Read more
KDE Plasma 6.7.2 Brings Fix For Most Common KWin Crash, Better Chromium Video Playback
KDE Plasma 6.7.2 is out today as the latest point release to deliver bug fixes for the Plasma 6.7 desktop that debuted earlier this month… ⌘ Read more
KDE Plasma 6.7.2 To Fix KWin’s Most Common Crash, Plasma 6.8 To Not Crash When Ejecting CDs
While Plasma 6.7.1 was just released this week following the recent stable debut of Plasma 6.7, there are already a number of fixes piling up for Plasma 6.7.2 due out in July. Plus more feature work and fixes for Plasma 6.8 as the next desktop version going Wayland-only… ⌘ Read more
@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.
Linux 7.2 Fixes Where PCIe Devices Could Be Inadvertently Restricted To 2.5 GT/s
The PCI/PCIe subsystem changes have been merged this week as we approach the end of the Linux 7.2 merge window… ⌘ Read more
NTFS3 Driver Sees Bug Fixes & Minor Improvements With Linux 7.2
While the new NTFS file-system driver merged for Linux 7.1 and has seen more improvements for Linux 7.2, for now at least the NTFS3 kernel driver continues to be maintained with new fixes and improvements. NTFS3 is the driver that was upstreamed to the Linux kernel a few years ago back during the pandemic by Paragon Software… ⌘ Read more