When I realize the “quick fix” from 2019 is already 7 years old ⌘ Read more

@bender@twtxt.net Ooops fixed 😅

When I head into the weekend after helping another team fix their bug ⌘ Read more

When a coworker’s code crashes because of a hardcoded “Sure, here’s what should fix the bug:” ⌘ Read more

My hoster broke UDP, so DNS is broken as well and that takes a lot of things with it. No more email for me, I guess.

Let’s hope they’ll fix it soon.

When the client sends me their list of “just 2 or 3 small things to fix” ⌘ Read more

When they ask how I fixed the bug but it was actually ChatGPT who did it. ⌘ Read more

@bender@twtxt.net Fixed 🤣 Nobody was following that feed 😅 yarnd had no reason to “pull” it in.

@javivf@adn.org.es Oh! Thanks, should be fixed now. 😊

Yikes. https://adamj.eu/tech/2021/05/13/python-type-hints-how-to-fix-circular-imports/

When I fix a bug and the behavior gets even weirder ⌘ Read more

Heh I thought I fixed that bug? (is it s abug?!)

@shinyoukai@neko.laidback.moe Okay I pushed a commit that hopefully fixes this. I hope!

@shinyoukai@neko.laidback.moe if you don’t show me the actual full stacktrace, I can’t fix the problem 😢

Most of it should work on other platforms, the bytecode VM that is. You may run into some platform quirks though that rely on syscall() – Let me know what you run into and I’ll try to fix them nw. The problem right now is I haven’t even begun to start work on another platform/architecture yet.

Hey folks! We have recently had a wonderful new release of #py5, read about the new 3D trimesh integration feature and the matplotlib TextPath integration.
That release was quickly followed by a release to fix some small issues that surfaced this last week. Please check out py5 0.10.9a1 and join us at https://github.com/py5coding/py5generator/discussions to share your experiences!

#CreativeCoding #Processing #Python #genuary (sorry for the hashtag spamming, I couldn’t resist!)

@bender@twtxt.net I also went back to my duty today and fixed a problem I created right before vanishing into the holidays. Of course, I discovered more problems while fixing the one thing. Luckily, another public holiday tomorrow. :-)

During my time off, I was a very lazy rat. I planned on doing some woodworking again, but instead I started watching Itchy Boot’s Africa season: https://www.youtube.com/watch?v=pMvfS5mbsiI&list=PL8M9dV_BySaXNvQ_V1q4UU-DirPQlX0ZP

@lyse@lyse.isobeef.org It’s already fixed:

https://github.com/openbsd/src/commit/668f1f05e71c5e979d278f1ad4568956226715ea

Question is when that fix will land. 😅

At around 19 seconds in the video, you can see some minor graphical glitches.

Text mode applications in Unix terminals are such a mess. It’s a miracle that this works at all.

In the old DOS days, you could get text (and colors) on the screen just by writing to memory, because the VGA memory was mapped to a fixed address. We don’t have that model anymore. To write a character to a certain position, you have to send an escape sequence to move the cursor to that position, then more escape sequences to set the color/attributes, then more escape sequences to get the cursor to where you actually want it. And then of course UTF-8 on top, i.e. you have no idea what the terminal will actually do when you send it a “🙂”.

Mouse events work by the terminal sending escape sequences to you (https://www.xfree86.org/current/ctlseqs.html#Mouse%20Tracking).

ncurses does an amazing job here. It’s fast (by having off-screen buffers and tracking changes, so it rarely has to actually send full screen updates to the terminal) and reliable and works across terminals. Without the terminfo database that keeps track of which terminal supports/requires which escape sequences, we’d be lost.

But gosh, what a mess this is under the hood … Makes you really miss memory mapped VGA and mouse drivers.

Hurray, I finally fixed another rendering bug in tt that was bugging me for a long time. Previously, when there were empty lines in a markdown multiline code block, the background color of the code block had not been used for the empty lines. So, this then looked as if there were actually several code blocks instead of a single one.

Image

I just fixed another bug in tt where the language hint in multiline markdown code blocks had not been stripped before rendering. It just looked like it was part of the actual code, which was ugly. I now throw it away. Actually, it’s already extracted into the data model for possible future syntax highlighting.

@shinyoukai@neko.laidback.moe Because you might not want to commit all changed files in a single commit. I very often make use of this and create several commits. In fact, I like to git add --patch to interactively select which parts of a file go in the next commit. This happens most likely when refactoring during a feature implementation or bug fix. I couldn’t live without that anymore. :-)

If you have a much more organized way of working where this does not come up, you can just git commit --all to include all changed files in the next commit without git adding them first. But new files still have to be git added manually once.

When the lead dev tells me he fixed a couple of bugs in my project over the holidays ⌘ Read more

Whoo! I fixed one of the hardest bugs in mu (µ) I think I’ve had to figure out. Took me several days in fact to figure it out. The basic problem was, println(1, 2) was bring printed as 1 2 in the bytecode VM and 1 nil when natively compiled to machine code on macOS. In the end it turned out the machine code being generated / emitted meant that the list pointers for the rest... of the variadic arguments was being slot into a register that was being clobbered by the mu_retain and mu_release calls and effectively getting freed up on first use by the RC (reference counting) garbage collector 🤦‍♂️

@zvava@twtxt.net By hashing definition, if you edit your message, it simply becomes a new message. It’s just not the same message anymore. At least from a technical point of view. As a human, personally I disagree, but that’s what I’m stuck with. There’s no reliable way to detect and “correct” for that.

Storing the hash in your database doesn’t prevent you from switching to another hashing implementation later on. As of now, message creation timestamps earlier than some magical point in time use twt hash v1, messages on or after that magical timestamp use twt hash v2. So, a message either has a v1 or a v2 hash, but not both. At least one of them is never meaningful.

Once you “upgrade” your database schema, you can check for stored messages from the future which should have been hashed using v2, but were actually v1-hashed and simply fix them.

If there will ever be another addressing scheme, you could reuse the existing hash column if it supersedes the v1/v2 hashes. Otherwise, a new column might be useful, or perhaps no column at all (looking at location-based addressing or how it was called). The old v1/v2 hashes are still needed for all past conversation trees.

In my opinion, always recalculating the hashes is a big waste of time and energy. But if it serves you well, then go for it.

@zvava@twtxt.net I might misunderstand what you wrote, but only hashing the message once and storing the hash together with the message in the database seems a way better approch to me. It’s fixed and doesn’t change, so there’s no need to recompute it during runtime over and over and over again. You just have it. And can easily look up other messages by hash.

When production runs all day without an incident after a major fix ⌘ Read more

@lyse@lyse.isobeef.org I was surprised by that as well. 😅 I thought these were features that you can use, but no, you must do all this.

By the way, I now fixed the issue that I mentioned at the end and it works on the netbook now. 🥳

Image

When I’ve already been struggling for hours to fix a bug ⌘ Read more

I finished all 12 days of Advent of Code 2025! #AdventOfCode https://adventofcode.com — did it in my own language, mu (Go/Python-ish, dynamic, int/bool/string, no floats/bitwise). Found a VM bug, fixed it, and the self-hosted mu compiler/VM (written in mu, host in Go) carried me through. 🥳

Need to fix:

• threads
  -media and links

I think i may have fixed threading too but can’t easily test now as i’ve left for my
holiday and don’t really use Mastodon 😂

@therealprologic@bridge.twtxt.net Sweet! Mentions are fixed! 👌 Now just have to fix threading!

@aelaraji@aelaraji.com Thanks for the account! I figured out one thing at least so far, my WAF was blocking some of the AP requests. Fixed that. Anyway, holiday time 🤣 Back in ~2 weeks.

@shinyoukai@neko.laidback.moe I don’t even know how to fix that 🤣 Do you? 🤔

Alright, this yarnd installation has been properly fixed.

When I try to fix the intern’s bug even though I don’t understand it myself ⌘ Read more

construir coisas na internet passou a ter premissas tão complexas que uma pessoa se esquece de como se fazia. Ando a re-adoptar esta metodologia, que hoje em dia já soa a punk

(entrevista com o Joshua Schachter, criador do del.icio.us)

Image

@movq@www.uninformativ.de That’s what tests are for. To fix them. :-D

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/

When I realize I’ve been trying to fix a bug all day in the wrong project ⌘ Read more

Test (_did I fix this shit™-)?

Hey @manton@bridge.twtxt.net 👋 Why yes I believe I did!

whoo fix a long stnading bug with identicons for feeds with no avatar in their metadata

Hint:

# nick = ...
# avatar = ...

Fixed

Ignite Realtime Blog: First release candidate of Smack 4.5 published
The Smack developers are happy to announce the availability the first release candidate (RC) of Smack 4.5.0.

The upcoming Smack 4.5 release contains many bug fixes and improvements. Please consider testing this release candidate in your integration stages and report back any issues you may found. The more people are actively testing release candidates, the less issues will remain in the actual release.

Smac … ⌘ Read more

Noelle’s royal ass fixed Black Clover ⌘ Read more

When the project manager tells me “it’s just a quick little fix” ⌘ Read more

Not even a Spell checker can fix that ☝️ so … sed -e 's/replay/reply' -e 's/gave/have

When I end my day fixing a bug ⌘ Read more

When I fix a bug in prod before anyone notices ⌘ Read more

A mate just sent me Microsoft’s magnificent master piece diagram regarding the end of life of Windows 10: https://support.microsoft.com/de-de/windows/windows-10-support-wurde-am-14-oktober-2025-eingestellt-2ca8b313-1946-43d3-b55c-2b95b107f281

That’s what you get for training with zalgo. :-D Of course, this isn’t even proper German.

In case they fix it, here’s a screenshot of the enlarged frontal crash:

Image

Just FTR, in case this wasn’t obvious, the “right to repair” (if there ever is one) needs to be more than just “you’re legally allowed to repair stuff”.

I just fixed this thing by replacing two capacitors. Great, but this was an absolute shitshow and it took several days. So many obstacles, everything’s tiny, connectors glued together, … It worked in the end, but I was so close to giving up.

Being legally allowed to do something is basically worthless if it’s not feasible to actually do it.

@movq@www.uninformativ.de I guess I wasn’t talking about the speed of interesting text/context, but more the “slowness” of these tools. I think I can build/ solutions and fix bugs faster most of the time? Hmmm 🤔 I think the only thing it’s able to do better than me is grasp large codebases and do pattern machines a bit better, mostly because we’re limited by the interfaces we have to use and in my ase being vision impaired doesn’t help :/

Fixed following page template bug so cached feed counts render without errors. cc @bender@twtxt.net

See if that fixes it? hmmm

Oh, also, have you fixed https://meet.mills.io/call/Yarn.social already? It didn’t work the other day.

@lyse@lyse.isobeef.org Hm, that might actually be (partially) true. Some external CD drives (without such a weight) start to spin/wiggle when the drive spins up and down … Although I guess that’s not really the case for Audio CDs as they are run at a fixed low RPM value, I think. 🤔

@lyse@lyse.isobeef.org That’s from a radio / CD-player thingy that someone in my family gave me so that I can try to repair it. (Indeed, some capacitors have blown up. But if that doesn’t fix it, I don’t know what to do. 😅)

There’s nothing on the other side. This really is just a block of metal that acts as a weight.

Mathieu Pasquet: slixmpp v1.12
This version is out mostly to provide a stable version with compatibility with the newly released Python 3.14, there are nonetheless a few new things on top.

Thanks to all contributors for this release!

• Bug in MUC self-ping ( XEP-0410) that would create a traceback in some uses
  
• Bug in SIMS ( XEP-0447) where all media would be marked as inline
  
• Python 3.14 breakage
  

• Prono … ⌘ Read more

When I run into a bug I thought I had fixed weeks ago ⌘ Read more

When we have to fix a bug in a hurry without being able to run the project locally ⌘ Read more

Reeves urged to avoid ‘half-baked’ tax fixes in Budget
The think tank says the government should seize the opportunity to reform the tax system. ⌘ Read more

Reeves urged to avoid ‘half-baked’ tax fixes in Budget
The think tank says the government should seize the opportunity to reform the tax system. ⌘ Read more

Reeves urged to avoid ‘half-baked’ tax fixes in Budget
The think tank says the government should seize the opportunity to reform the tax system. ⌘ Read more

I disabled the compression of logs on my edge, which I’m hoping will fix the “instability” I see every now and again where my edge network just “falls off the face of the earth”. Some folks don’t really appreciate / understand this, but Disk I/O can kill your application(s) no matter what. I/O Wait is a real thing.

OCaml 5.4 Release: New Features, Fixes, and More
Comments ⌘ Read more

Water bills to rise further for millions after regulator backs extra price increases
Five water companies win permission for higher bills as they seek more funds to fix outdated infrastructure. ⌘ Read more

Water bills to rise further for millions after regulator backs extra price increases
Five water companies win permission for higher bills as they seek more funds to fix outdated infrastructure. ⌘ Read more

Water bills to rise further for millions after regulator backs extra price increases
Five water companies win permission for higher bills as they seek more investment to fix outdated infrastructure. ⌘ Read more

Water bills to rise further for millions after appeal
Five water companies win permission for higher bills as they seek more investment to fix outdated infrastructure. ⌘ Read more

Water bills to rise further for millions after appeal
Five water companies win permission for higher bills as they seek more investment to fix outdated infrastructure. ⌘ Read more

The fix to the iPhone Antennagate in 2010 was 20 bytes
Comments ⌘ Read more

Unlimited access to Docker Hardened Images: Because security should be affordable, always
Every organization we speak with shares the same goal: to deliver software that is secure and free of CVEs. Near-zero CVEs is the ideal state. But achieving that ideal is harder than it sounds, because paradoxes exist at every step. Developers patch quickly, yet new CVEs appear faster than fixes can ship. Organizations standardize on… ⌘ Read more

Four new stable kernels
The 6.17.1, 6.16.11, 6.12.51, and 6.6.110 stable kernels have been released.
This time around, they contain a relatively small number of important fixes
in various parts of the kernel. ⌘ Read more

OpenSSH 10.1 released
OpenSSH 10.1 has
been released. Along with “a minor security fix” and some other bug
fixes, this release disallows control characters in user names passed via
the command line, adds better logging around certificate refusals, and a
new RefuseConnection server configuration option. ⌘ Read more

Buyers could save hundreds in new house buying shakeup
Housing Secretary Steve Reed claims the changes would “fix the broken system” and put more money “back into working people’s pockets”. ⌘ Read more

Apple Releases Safari Technology Preview 229 With Bug Fixes and Performance Improvements
Apple today released a new update for Safari Technology Preview, the experimental browser that was first introduced in March 2016. Apple designed ‌Safari Technology Preview‌ to allow users to test features that … ⌘ Read more

Seven new stable kernels
Greg Kroah-Hartman has announced the release of the 6.16.10, 6.12.50, 6.6.109, 6.1.155, 5.15.194, 5.10.245, and 5.4.300 stable kernels. All of these kernels
have lots of important fixes throughout the kernel tree. ⌘ Read more

Apple Provides Fix for iMessage Activation Bug in iOS 26
Apple this week provided troubleshooting steps for iPhone owners who are unable to activate iMessage with a phone number in iOS 26.

Image

According to Apple, some customers might not be able to activate iMessage with a phone number … ⌘ Read more

OpenSUSE Leap 16 released
The openSUSE\
Leap 16 release is now available.

This major version update of our fixed-release community-Linux
distribution has a fresh software stack and introduces an unmatched
maintenance- and security-support cycle, a new installer and
simplified migration options.

See our look at this release for more
information. ⌘ Read more

MacOS Sequoia 15.7.1 & MacOS Sonoma 14.8.1 Updates Released with Security Fixes
Apple has released MacOS Sequoia 15.7.1 and MacOS Sonoma 14.8.1 as security patch releases for Mac users who are not yet running the Tahoe operating system, of which MacOS Tahoe 26.0.1 was just released. The updates are focused on security patches and do not include any other changes or features for the Sequoia or Sonoma … [Read More](https://osxdaily.com/2025/09/30/macos- … ⌘ Read more

MacOS Tahoe 26.0.1 Update Released to Fix Mac Studio Installation Bug
Apple has issued MacOS Tahoe 26.0.1 as a software update for Tahoe users. The update focuses primarly on resolving an issue for Mac Studio owners who were not able to install the initial MacOS Tahoe 26 release onto the M3 Ultra version of the Studio. Apparently other bug fixes and security improvements are included as … [Read More](https://osxdaily.com/2025/09/29/macos-tahoe-26-0-1-update-releas … ⌘ Read more

iOS 26.0.1 Update Released to Fix Various iPhone 17 Issues, & Blank Screen Icons
Apple has released the first update for iOS 26.0.1, which includes a handful of bug fixes specifically aimed at the new iPhone 17 lineup, as well as addressing an issue for all devices where Home Screen icons can appear blank after using various Liquid Glass customization settings, and another issue where VoiceOver might disable itself … [Read More](https://osxdaily.com/2 … ⌘ Read more

CodeQL zero to hero part 5: Debugging queries
Learn to debug and fix your CodeQL queries.

The post CodeQL zero to hero part 5: Debugging queries appeared first on The GitHub Blog. ⌘ Read more

@itsericwoodward@itsericwoodward.com No worries, all good, mate! We all have to start somewhere. Other software requests my feed several orders of magnitude more often.

I can confirm, the User-Agent header appears to be fixed. \o/

Two other things I noticed, though:

1. There’s now an OPTIONS request for my feed coming from something that claims to be Firefox, pointing to your feed URL in the query. No clue what this is about. In any case, it’s rejected with a 405 Method Not Allowed.

2. Not that these few requests bother me at all, but you might wanna implement caching next with either the If-Modified-Since or If-None-Match request headers. This way, if the feed hasn’t changed, the web server can reply with a 304 Not Modified and no body at all, saving unnecessary traffic. But again, this is really not an issue for me at all. I just wanted to make sure you’re aware of it, that’s all. It might be even already on your agenda. Or you might decide to never do anything about it, which is also fine for me. :-)

I think I’m just about ready to go live with my new blog (migrated from MicroPub). I just finished migrating all of the content over, fixing up metadata, cleaning up, migrating media, optimizing media.

The new blog for prologic.blog soon to be powered by zs using the zs-blog-template is coming along very nicely 👌 It was actually pretty easy to do the migration/conversation in the end. The results are not to shabby either.

Before:

• ~50MB repo
  
• ~267 files
  

After:

• ~20MB repo
  
• ~88 files

@movq@www.uninformativ.de Yeah I was gonna say 😅 The problem isn’t that bad 🤣 But still we should fix this soon™ 🔜

DietPi September 2025 Update Brings Faster Backups and Roon Server Early Access
The September 20th release of DietPi v9.17 introduces smaller and more efficient system images, faster backups with reduced disk usage, and a new toggle for Roon Server’s early access builds. The update also addresses SPI bootloader flashing issues on Rockchip devices, improves Raspberry Pi sound card handling, and includes multiple bug fixes across tools and […] ⌘ Read more

@bender@twtxt.net Yup! Fixing that now! 👌 Also the Tags page and the size of the trags is intentional, as more posts are tagged with the same tag, those will result in larger size rendered tags in a kind of “tag cloud” – At this this is the intention.

@prologic@twtxt.net to clarify: i meant the ability to parse feeds using unix command line utilities, as a principal of twtxtv1’s design. im not sure how feasible it is to build a simple feed reader out of common scripting utilities when hashing is in play, and;

i concede, it does make a lot of sense to fix up the hashing spec rather than completely supplant it at this point, just thinking about what the rewrite would be like is dreadful in and of itself x.x

MacOS Tahoe 26 Feels Slow? Try These 6 Performance Tips
Some Mac users who have updated to macOS Tahoe 26 feel like the new operating system runs slower than their prior MacOS installation did. Reports online suggest there can be general sluggishness and lagging performance, sometimes with frame rate drops and stuttering animations on the screen, or even when typing. Other users in various forums … Read More ⌘ Read more

Of course we still have to fix the hashing algorithm and length.

A step-by-step guide to modernizing Java projects with GitHub Copilot agent mode
Learn how to use GitHub Copilot agent mode to modernize legacy Java projects with guided upgrades, automated fixes, and cloud-ready migrations.

The post A step-by-step guide to modernizing Java projects with GitHub Copilot agent mode … ⌘ Read more

@lyse@lyse.isobeef.org I don’t think there’s any point in continuing the discussion of Location vs. Content based addressing.

I want us to preserve Content based addressing.

Let’s improve the user experience and fix the hash commission problems.

@alexonit@twtxt.alessandrocutolo.it I took it down mostly because of continued abuse and spam:l. I intend to fix I and improve the drive and its sister at Summer point 🤞

iOS 26 Battery Life Suffering? Here’s Why & How to Fix It
iOS 26 is in the wild, and aside from the mixed reactions to the Liquid Glass interface, there are also wildly different reports of battery life performance post-update. A notable number of iPhone and iPad users are complaining throughout social media and online forums that iOS 26 battery drains faster than it did before, and … Read More ⌘ Read more

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

Mathieu Pasquet: slixmpp v1.11
This new version includes a few new XEP plugins as well as fixes, notably
for some leftover issues in our rust JID code, as well as one for a bug that
caused issues in Home Assistant.

Thanks to everyone who contributed with code, issues, suggestions, and reviews!

Nicoco put in a lot of work in order to get all possible wheels built in CI. We now have manylinux and musl builds of everything doable within codeberg,
published to the codeberg pypi repo, and published on pypi. … ⌘ Read more

ACCC accuses four Aldi vegetable suppliers of fixing prices
The Australian Competition and Consumer Commission accuses growers of forming a cartel to fix prices of vegetables supplied to Aldi in three states. ⌘ Read more

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.