My elders complained when rotary phones lost their wheel, getting replaced by push buttons. It was mayhem! We don’t live in a Matrix, we live in a loop. LOL.

@movq@www.uninformativ.de Yeah, give it a shot. At worst you know that you have to continue your quest. :-)

Fun fact, during a semester break I was actually a little bored, so I just started reading the Qt documentation. I didn’t plan on using Qt for anything, though. I only looked at the docs because they were on my bucket list for some reason. Qt was probably recommended to me and coming from KDE myself, that was motivation enough to look at the docs just for fun.

The more I read, the more hooked I got. The documentation was extremely well written, something I’ve never seen before. The structure was very well thought out and I got the impression that I understood what the people thought when they actually designed Qt.

A few days in I decided to actually give it a real try. Having never done anything in C++ before, I quickly realized that this endeavor won’t succeed. I simply couldn’t get it going. But I found the Qt bindings for Python, so that was a new boost. And quickly after, I discovered that there were even KDE bindings for Python in my package manager, so I immediately switched to them as that integrated into my KDE desktop even nicer.

I used the Python KDE bindings for one larger project, a planning software for a summer camp that we used several years. It’s main feature was to see who is available to do an activity. In the past, that was done on a large sheet of paper, but people got assigned two activities at the same time or weren’t assigned at all. So, by showing people in yellow (free), green (one activity assigned) and red (overbooked), this sped up and improved the planning process.

Another core feature was to generate personalized time tables (just like back in school) and a dedicated view for the morning meeting on site.

It was extended over the years with all sorts of stuff. E.g. I then implemented a warning if all the custodians of an activitiy with kids were underage to satisfy new the guidelines that there should be somebody of age.

Just before the pandemic I started to even add support for personalized live views on phones or tablets during the planning process (with web sockets, though). This way, people could see their own schedule or independently check at which day an activity takes place etc. For these side quests, they don’t have to check the large matrix on the projector. But the project died there.

Here’s a screenshot from one of the main views: https://lyse.isobeef.org/tmp/k3man.png

This Python+Qt rewrite replaced and improved the Java+Swing predecessor.

@javivf@adn.org.es not having any issues on my M4 mini, no. Smooth. There are some visual discordances I don’t like, but if I give them a blind eye I can live with them. 😅

We had some gray soup with the occasional fine rain with strong wind gusts. Despite the bad forecast we took the train to Geislingen/Steige and strolled up to the Helfenstein castle ruin. All the colorful leaves were so beautiful, it didn’t matter that the sun was behind thick layers of clouds.

We then continued to the Ödenturm (lit. boring tower). By then the wind had picked up by quite a bit, just as the weatherman predicted. We were very positively surprised that the Swabian Jura Association had opened up the tower. Between May and October, the tower is typically only manned on Sundays and holidays between 10 and 17 o’clock. But yesterday was Saturday and no holiday. The lovely lady up there told us that they’re currently experimenting with opening up on Saturday, too, because there are some highly motivated members responsible for the tower.

We were the very first visitors on that day. Last Sunday, when the weather lived up to the weekday’s name, they counted 128 people up in the tower. Very impressive.

The wind gusts were howling around the tower. Luckily, there are glass windows. So, it was quite pleasant up in the tower room. Chatting with the tower guard for a while, we got even luckier: the sun came out! That was really awesome. The photos don’t do justice. As always, it looked way more stunning in person.

Thanks to all the volunteers who make it possible to enjoy the view from the thirty odd meters up there. That certainly made our day!

After signing the guestbook we climbed down the staircase and returned to the station and headed back. The train even arrived on time. What a great little trip!

https://lyse.isobeef.org/wanderung-auf-die-burgruine-helfenstein-und-den-oedenturm-2025-10-25/

@thecanine@twtxt.net I am not arguing you didn’t do the right thing™, and even if the impact is minimal, or nothing, you did what you thought was right (and I agree). I don’t agree with certain rules the EU wants to impose, not in this particular case. There are rotten potatoes everywhere, and I don’t get fooled by the EU often sacrosanct behaviour.

But who am I to say anything, right? Look at the grotesque clown utterly shit show we live with on this side!

@bender@twtxt.net See the problem is you don’t live in the “busy” enough 😂 There are roaches everywhere here! 🤣 LOL snakes too! Plovers, Magpies, Crows, Spiders, even Deer for fucks sake 😂

From the chicken archive, 2017.

Not mine, these were more or less free roaming chickens. Farmers didn’t use some of their fields for a while and allowed some other farmer to let the birds live there in the meantime.

(Full resolution, CC BY-SA.)

@movq@www.uninformativ.de So damn true.

I have a friend that might lock himself out of his home if there’s a power outage while I keep removing apps and devices from my daily lives instead.

I recently switched from all the todo apps I used to sticky notes on my monitors and a pocket notebook for sketching and quick notes.

@zvava@twtxt.net

(#abcdefghijkl https://example.com/tw.txt#:~:text=2025-10-01T10:28:00Z), because it can be simply hacked in to clients currently on hashv1 and provides an off-ramp to location-based addressing

I like that property (an off-ramp to location-based addressing), so I think I could live with that approach. ✅

(I’m not sure why we’re using text fragments, though. Wouldn’t that link to the first occurence of 2025-10-01T10:28:00Z? That’s not necessarily correct. And, to be proper URLs that Firefox and Chromium understand, it would also need to be written as 2025%2D10%2D01T10:28:00Z. The dash carries meaning, sadly. I think all this just creates needless complication. How about we just go with https://example.com/tw.txt#2025-10-01T10:28:00Z?)

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

@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!

@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!

Here is just a small list of things™ that I’m aware will break, some quite badly, others in minor ways:

1. Link rot & migrations: domain changes, path reshuffles, CDN/mirror use, or moving from txt → jsonfeed will orphan replies unless every reader implements perfect 301/410 history, which they won’t.
   
2. Duplication & forks: mirrors/relays produce multiple valid locations for the same post; readers see several “parents” and split the thread.
   
3. Verification & spam-resistance: content addressing lets you dedupe and verify you’re pointing at exactly the post you meant (hash matches bytes). Location anchors can be replayed or spoofed more easily unless you add signing and canonicalization.
   
4. Offline/cached reading: without the original URL being reachable, readers can’t resolve anchors; with hashes they can match against local caches/archives.
   
5. Ecosystem churn: all existing clients, archives, and tools that assume content-derived IDs need migrations, mapping layers, and fallback logic. Expect long-lived threads to fracture across implementations.

We’ve been discussing the idea of changing the threading model from Content-based Addressing to Location-based addressing for years now. The problem is quite complex, but I feel I have to keep reminding y’all of the potential perils of changing this and the pros/cons of each model:

With content-addressed threading, a reply points at something that’s intrinsically identified (hash of author/feed URI + timestamp + content). That ID never changes as long as the content doesn’t. Switching to location-based anchors makes the reply target extrinsic—it now depends on where the post currently lives. In a pull-based, decentralised network, locations drift. The moment they do, thread identity fragments.

@lyse@lyse.isobeef.org check out their song zenbu kakete go!!

it’s very sleek and smooth and just so vibe-y!!! also this live performance

has an EPIC intro featuring ichika (violin girl) plus one of the members beatboxing and two girls (including my all time favorite idol, dambara ruru!) on vocals! it’s so good

Do I buy a new monitor or do I live with the burn-ins all the time? It’s getting annoying. When I edit images in GIMP, I have to double check if something is a pixel or a burn-in.

have you ever wanted to see an idol play violin live on stage? your wish has been granted

@prologic@twtxt.net what a great world we live in! No wonder they marked this sector unoccupied.

We finally got a caliper donated for this year’s scout flea market. We didn’t sell it, but kept it ourselves. It will come in very handy every now and then in our material store. For example, I missed having a caliper in the past when sorting our random assortment of screws or measuring the depth of a hole. It’s a wee bit banged up (probably happened during transport) and didn’t come with a box, but the latter is now solved.

The lid and bottom came from a wardrobe back panel I got from a mate, the sides were rocket sticks in their former lives. I found some scrap of felt in our material store and some hinges laying around in the drawers of my own workshop.

Unfortunately, the table saw teared up the plywood veneer fibres badly, even though I put tape around to prevent that. This is the first time it didn’t work. At. All. To cover that up, I painted the box with some decades old tinting paint (price tag says Deutsche Mark, not Euro!) from my paint cabinet. It’s awesome, works absolutely perfectly and doesn’t smell the slightest bit. I reckon, this caliper box is plenty good enough for occasional use at our scout material store.

@movq@www.uninformativ.de Yeah, luckily, there is the suckless project. I couldn’t live without dmenu!

We’re entering the “too hot to think”-season in 3, 2, 1 … and we’re live!

@prologic@twtxt.net I am finding writing my Notes very therapeutic. Just create a markdown file and commit, push, and it’s live. Whatever comes to mind, whatever I want to keep as relevant. Silly things, more like a dump.

If I feel like it, I do. If not, I don’t. Not social, not intended for anyone to see them. I am enjoying it!

@movq@www.uninformativ.de Hmmm, that indeed surprises me, too. Looks like I live in a moorhen shortage area. Even ducks and geese are not all that common. But then also, there aren’t any substantially sized lakes around here. Just a few smaller ponds, which I don’t visit all that often.

@lyse@lyse.isobeef.org Thanks. 😅 Quite a few of them waddle around at the pond in our village. But those two individuals were seen in a nearby zoo. They’re not zoo animals, they just live there. 😅

live low in real life but live fast online 😝😝😝

@prologic@twtxt.net You can read more about the “cryptic” live coding language Punctual in my newsletter

Hey y’all 👋 I am told my “participation” is drastically down of ,ate So sorry 😞 Busy quite a busy few weeks at work with a reorg and lots of complex things happening in real live too 😅 – Hope everything is doing well 🤗

And to finish the day: Om Live at Pioneer Works 🤘 – https://www.youtube.com/watch?v=IwnDKcoVHmY

@movq@www.uninformativ.de Also the so-called “deadline” isn’t set it stone. We’re all busy people with day jobs and lives, so we may have to move it anyway 😅

“Forgive me for the harm I have caused this world. None may atone for my actions but me and only in me shall their stain live on. I am thankful to have been caught, my fall cut short by those with wizened hands. All I can be is sorry, and that is all I am.”

that said, and reading to @sorenpeter@darch.dk and @andros@twtxt.andros.dev I have new thoughts. I assume that this won’t change anyone’s opinions or priorities, so it makes no harm sharing them.

It’s always tempting to use something that already exists (like X, Masto, Bsky, etc.) rather that building anything through effort and disagreement until reaching to something useful and valuable together. A ‘social service’ is only useful if people is using it.

I’ll add that I haven’t lost interest on the ‘hacky’ part of twtxt about developing tools, protocols, and extensions as a community. It’s the appealing part! It’s a nice hobby to have, shared with random people across the world.
But this is not the right way for me, and makes me feel that I’m unwelcome to propose something different (after watching replies to my previous twt). Feels like “If you don’t agree, you are free to leave, we’ll miss you.” Naah, not cool. I’ve lived that many times before, and nowadays I don’t have enough spare time and energy for a hobby like that.

Let’s see what happens next with the micro-community!

There are reports of widespread power cuts in Spain and Portugal
Comments ⌘ Read more

Reports of widespread power cuts in Spain and Portugal
Comments ⌘ Read more

@bmallred@staystrong.run yeah! you’re right. Unfortunately, Decaf isn’t a thing where I live 🤷

@kat@yarn.girlonthemoon.xyz Yes see UPGRADE.md – I believe @xuu@txt.sour.is is now running this live after a couple of hiccups and a bug fix. So yeah if you can, that would be cool, basically looking for early beta testers (I was the alpha tester 🤣)

Show HN: Lemon Slice Live, a real-time video-audio AI model
Comments ⌘ Read more

About the nuclear power plant on the Moon, they are beating us. There was a time we were ahead, but I understand nothing lasts forever. Now, being a world power for only one hundred and twenty some years, and a super power for around seventy sure is a record (as in short-lived). The Roman Empire lasted over 500 years!

@prologic@twtxt.net “curated” channels (you can see the guide to see the topics it covers), without the ability to fast forward, nor pause. You know, like live television.

@prologic@twtxt.net your live posting when something goes wrong is environmental storytelling it’s so funny help

Pope Francis dies aged 88
Comments ⌘ Read more

@sorenpeter@darch.dk woah! Soren lives! 😅😂

Welcome back!

@sorenpeter@darch.dk woah! Soren lives! 😅😂

Welcome back!

Fedora change aims for 99% package reproducibility
The effort to ensure that open-source software is reproducible has been gathering steam over the years, and gaining traction with major Linux distributions. Debian, for example, has been working toward reproducible builds for more than a decade; it can now produce official live CDs of the current stable release that are reproducible. Fedora started on the path much later, but it has progressed far enough that the project is now con … ⌘ Read more

I left XMPP because I found no interactions. Long live IRC!

Tunarr: Create and configure live TV channels from media on your servers
Comments ⌘ Read more

No code is dead. Long live vibe coding
Comments ⌘ Read more

Live Map of the London Underground
Comments ⌘ Read more

@aelaraji@aelaraji.com Yeah I’m in the process of rewriting (incrementally) the cache storage backend. It’s now been live for at least a week now and pagination and peering are the last things left to do 🤞

@prologic@twtxt.net I can live without highlights. Actually, I prefer not to have them. A good search is all I want.

Llama 4 Now Live on Groq
Comments ⌘ Read more