Gemini Starts Rolling Out On Android Auto
Gemini is (finally) rolling out on Android Auto, replacing Google Assistant while keeping “Hey Google,” adding Gemini Live (“let’s talk live”), message auto-translation, and new privacy toggles. “One feature lost between Assistant and Gemini, though, is the ability to use nicknames for contacts,” notes 9to5Google. From the report: Over the past 24 hours, Google has quietly started the rollou … ⌘ Read more

OpenAI CFO Says Company Isn’t Seeking Government Backstop, Clarifying Prior Comment
OpenAI CFO Sarah Friar said late Wednesday that the AI startup is not seeking a government backstop for its infrastructure commitments, clarifying previous comments she made on stage during the Wall Street Journal’s Tech Live event. From a report: At the event, Friar said OpenAI is looking to create an ecosyste … ⌘ Read more

43% of Gen Z Prefer YouTube and TikTok To Traditional TV and Streaming
A new Activate Consulting report reveals that 43% of Gen Z now prefer YouTube and TikTok over traditional TV or paid streaming. With global media revenues surging and traditional TV viewership collapsing, the average person now spends over 13 hours a day consuming content across platforms, effectively living a “32-hour day” th … ⌘ Read more

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

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

Cycling is fun in itself, but doing it to perform a task is extremely satisfying. It feels so good to load up the cargo rack with groceries, or to opt for a bicycle instead of a car to go visit a friend. Biking with a purpose makes my desire to live green feel much more tangible.

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

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.

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.

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

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

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

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

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.

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

Welcome back!

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

Welcome back!

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

re reading so NewRAMStorage(…) is just something that setups your storage and initial data.. that can probably live with storage/sqlite. The point is the storage package does not import the implementations of storage.Storage It just defines the contract for things that use that interface. Now storage/sqlite CAN import storage and not have a circle dep.

It kinda works in reverse for import directions. usually you have your root package that imports things from deeper in the directory structures.. but for the case of interfaces it reverses where the deeper can import from parents but parents cannot import from children.

- app < storage
      < storage/sqlite
      < controller < storage
                   < storage/sqlite
 
- sqlite < storage

- storage X storage/sqlite

@prologic@twtxt.net @david@collantes.us Good question, was this on live TV? I think it was? 🤔

The correct way to do Drum and Bass. // Om Live at Pioneer Works // https://www.youtube.com/watch?v=IwnDKcoVHmY #NowPlaying

Got myself a proper bass amp and now I really want to live in a small house in the middle of nowhere, where I won’t bother anyone. 😅

I’ve implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:

• nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
  
• nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
  
• no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt
  

I’m not sure I like the leading @ thou…

Live from Piksel Festival in about an hour via: https://www.twitch.tv/pikselfest - Also other presentations stating momentary

I’m giving a shot talk about twtxt/yarn/timeline tommow around noon CET at Piksel Festival in Norway. More info and link for live stream at: https://24.piksel.no
(So I will most likely not be joining the call)

@xuu@txt.sour.is done, and done, and done. The three of us dropped our mail-in ballots, and received confirmation they are counted. Living in a red state (well, kid said it is more like purple now) makes me sad, and mad, but I have done what I can—and that includes explaining things to others, and encouraging them to vote.

Three days from today, towards the end of the day, we in the US will have an idea of who the nation’s presiding person will be for the next four years. In the 32 years I have lived here, I have never been more worried about an election outcome.

Inversion by Aric McBay was another random library pick. Like The Fall of Io, it’s the most recent in a series, though I think this series is pretty loosely connected. In contrast, the villain in this book is simple and cartoonishly evil. The book presents a design for utopia which was interesting but a little cloying. I’m not sure if I’m supposed to want to live there, but I don’t think I do. I enjoyed the book as easy reading, and might try the others in the series some time. (4/4)

I’m planning to be there tomorrow (message from yesterday, since we can not all live in the future;)

Reading about browser security measures and getting sad we don’t live in a world where cross-site scripting is a feature instead of a bug.

On My Blog:Real Life in Star Trek, Cost of Living https://john.colagioia.net/blog/2024/09/26/cost-living.html #scifi #startrek #closereading

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with “(#abc1234) Edit: …” and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

• Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

• “Clients MUST preserve the original hash” — do you mean they MUST preserve the original twt?

• Thanks for phrasing the bit about deletions so neutrally.

• I don’t like the MUST in “Clients MUST follow the chain of reply-to references…”. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

• Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

• For “who follows” lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

• Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

• Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

• I’m a little sad about other protocols being not recommended.

• I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

@movq@www.uninformativ.de I’m glad you like it. A mention (@<movq https://www.uninformativ.de/twtxt.txt>) is also long, but we live with it anyway. In a way a replyto: is just a mention of a twt instead of a feed/person. Maybe we chould even model the syntax for replies on mentions: (#<2024-09-17T08:39:18Z https://www.eksempel.dk/twtxt.txt>) ?!