@bender@twtxt.net Better safe than sorry, I guess. 😅
@prologic@twtxt.net nothing to be sorry about. It gave me time to watch TV with kids! 🤭
I am sorry folks 😞
… and now I just read @bender@twtxt.net’s other post that said the Gemini text was a shortened version, so I might have criticized things that weren’t true for the full version. Okay, sorry, I’m out. (And I won’t play that game, either. Don’t send me another AI output, possibly tweaked to address my criticism. That is besides the point and not worth my time.)
@lyse@lyse.isobeef.org believe it or not, I imagined the whole thing in my head, and kind of ROFLMAO. I am sure it was much, much less funny in real life. So, sorry! :-P
@bender@twtxt.net Oh! It’s all good, I was planning on retiring my TheLounge instance anyways and will stick to connecting directly for the occasional chat when needed. Cheers! (Sorry for the belated reply.)
Turned out I didn’t make it, sorry. Maybe next time. I hope you had a great yarn, @prologic@twtxt.net and @bender@twtxt.net, and didn’t waste any time waiting for me.
Lexical differential highlighting instead of syntax highlighting
Recently there is a lot of discussion around syntax highlighting ( 1, 2, 3), which reminds me of this old post I read a while ago.
Sieht ganz so aus, als hätte die gute @kat@yarn.girlonthemoon.xyz ihre Büchse mit in den Kurort Bad Gateway genommen.
Sorry, this pun only works in German, where “Bad” means spa and is used as prefix for spa towns.
It still needs some cleaning (and some slight UX improvements), but overall, I’m happy with it.
BTW - I promise, I intended it to be pronounced like “TweetStream” (or as written, “TwtStrm”), rather than “TweetStorm”. Sorry again. 😊
User-Agent header. Instead of the URL, the nick is repeated.
@lyse@lyse.isobeef.org Thanks, I think I fixed it now. Sorry for the spam.
@zvava@twtxt.net Going to have to hard disagree here I’m sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) I’m sorry you’ve completely lost me! I’m old enough to pre-date before Linux became popular, so I’m not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject) whose contents is a cryptographic content-addressable hash of the “thing”™ you’re replying to and forming a chain of other replies (a thread).
I’m sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a “Magic Date” for which our clients use the modified function(s).
@alexonit@twtxt.alessandrocutolo.it Holy fuck! 🤣 I just realized how bad my typing was in my reply before 🤣 🤦♂️ So sorry about that haha 😆 I blame the stupid iPhone on-screen keyboard ⌨️
Apologies if I’ve been spamming anyone out there in twtxt-land today.
I’ve been working on a couple of twtxt-related projects, and one of them is a reader (tentatively called twtstrm) written in JS. I used dummy data for the first few stages of development, but now I’m at the point where I need some real data, and that meant hitting up my actual following list.
Of course, it didn’t help that I had a typo in my If-Modified-Since headers, but all that has since been resolved.
Anyways, if I accidentally spammed you with requests today, I am sorry, and it shouldn’t happen anymore.
We thank you for your patience, and apologize for the inconvenience.
@zvava@twtxt.net oh duh! Sorry, I promised I read, my brain just didn’t process it right. I shall follow your progress, and offer bits and pieces of unrequested trivialities. :-)
@dce@hashnix.club Yeah, I’ve read about that approach. Sounds clever. Truth is, I’m too tired. 😢 I don’t want to spend too much of my time fighting assholes.
I’ve now started blocking entire cloud hosters. Sorry, not sorry.
/short/ if it's of this useless kind. Never thought that they ever actually will improve their Atom feeds. Thank you, much appreciated!
@kat@yarn.girlonthemoon.xyz @movq@www.uninformativ.de Sorry, I neither finished it nor in time. :-( That’s as good as it’s gonna get for the moment: https://git.isobeef.org/lyse/gelbariab/-/tree/master/rss-proxys?ref_type=heads
The README should hopefully provide a crude introduction. The example configuration file is documented fairly well, I believe (but maybe not). You probably still have to consult and maybe also modify the source code to fit your needs.
Let me know if you run into issues, have questions, wishes etc.
@movq@www.uninformativ.de According to this screenshot, KDE still shows good old application icons: https://upload.wikimedia.org/wikipedia/commons/9/94/KDE_Plasma_5.21_Breeze_Twilight_screenshot.png
And GNOME used to have them, too: https://upload.wikimedia.org/wikipedia/commons/9/9f/Gnome-2-22_%284%29.png
I like the looks of your window manager. That’s using Wayland, right? The only thing on this screenshot to critique is all that wasted space of the windows not making use of the full screen!!!1 At least the file browser. 8-)
This drives me nuts when my workmates share their screens. I really don’t get it how people can work like that. You can’t even read the whole line in the IDE or log viewer with all the expanded side bars. And then there’s 200 pixels on the left and another 300 pixels on the right where the desktop wallpaper shows. Gnaa! There’s the other extreme end when somebody shares their ultra wide screen and I just have a “regularish” 16:10 monitor and don’t see shit, because it’s resized way too tiny to fit my width. Good times. :-D
Sorry for going off on a tangent here. :-) Back to your WM: It has the right mix of being subtle and still similar to motif. Probably close to the older Windowses. My memory doesn’t serve me well, but I think they actually got it fairly good in my opinion. Your purple active window title looks killer. It just fits so well. This brown one (https://www.uninformativ.de/blog/postings/2025-07-22/0/leafpads.png) gives me also classic vibes. Awww. We ran some similar brownish color scheme (don’t recall its name) on Win95 or Win98 for some time on the family computer. I remember other people visting us not liking these colors. :-D
Woops, sorry if my Pod was offline for a few days, I hadn’t checked and needed to renew the domain xP
@doesnm.p.psf.lt@doesnm.p.psf.lt so sorry for your suffering, and loss. :-P
@bmallred@staystrong.run Oh sorry I should have explained those terms 🤦♂️
@bender@twtxt.net @aelaraji@aelaraji.com Sorry this was my fault 🤦 For whatever reason my pod had never seen that particular Twt from @movq@www.uninformativ.de – And… There’s a bit of a “behavioral” problem with the Trusted Peers functionality that means operators have to periodically re-trust peers manually 😭 Need to rework this 🤞
Passing of Jean-Raymond Abrial
Jean-Raymond Abrial, father (in particular!) of the Z notation, but also of the B method, and then Event-B, passed away on May 26. I was surprised to see that this piece of news, which may be of some interest to formal method folks, doesn’t seem to be very well known (there’s not much material on the web).
Here are some links (on LinkedIn, sorry):
[by Bertrand Meyer](https://www.linkedin.com/posts/bertrandmeyer_i-am-saddened-to-report-from-todays-print-activity-7335684948974034944-SJf1? … ⌘ Read more
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 🤗
@javivf@adn.org.es Sorry. 😂 Meet me on IRC at irc.mills.io in #edgeguard 👌 I’m @james@yarn.mills.io there 😅
“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.”
2009 facebook/VK look, it kind of feels notsalgic. (the tld is a .me not a .com if anyone else wants to take a look atit)
@aelaraji@aelaraji.com Oh, sorry it’s a typo. Also developer previously worked in vk (making mobile app afaik). Not he hates him xD
Hey @kat@yarn.girlonthemoon.xyz If you see this, I’m aware of a bug. I’m trying to figure it out and fix it. bare with me 🤗 It is what’s causing things to “stall” and to have to “restart”. Sorry 😞
@prologic@twtxt.net exciting!!!!!! i’m SO SORRY i didn’t get to doing the migration for my instance though - i’ve been really busy! T__T but i hope to get to it sometime this week i really wanna upgrade i think i’m just a bit nervous for whatever reason lol
@thecanine@twtxt.net Sorry, but you were expecting what now?! 🤣
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
I also fundamentally do not believe in the notion that Twtxt should be readable and writable by humans. We’ve thrown this “argument” around in support of some of the proposals, and I just don’t buy it (sorry). As an analogy, nobody writes Email by hand and transmits them to mail servers vai SMTP by hand. We use tools to do this. Twtxt/Yarn should be the same IMO.
git pull on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de oi, that has to be a bot. AI bot? Maybe not, but still a bot. I see this becoming more and more of an issue, sorry to say…
@twtxtory@twtxtory.adn.org.es sorry, it isn’t. After you enter the password, it takes a very long time to render anything. I don’t have the patience to wait. Longest I waited is 3 minutes, and nothing. Super extremely slow.
@prologic@twtxt.net oh, sorry, you are right. Beautiful 404. The most beautiful 404 I have ever seen. Tremendous! 🤪
@bender@twtxt.net Sorry! 🤣
@abucci@anthony.buc.ci totally my fault sorry 😞
Oh hey @rrraksamam@twtxt.net 👋 Welcome back! 🙌 Sorry about the data loss 🤯
SqliteCache backend I'm working on here, what are your thoughts regarding mgirations from old MemoryCache (which is now gone in the codebase in this branch). Do you care to migrate at all, or just let the pod re-fetch all feeds? 🤔
I don’t think I’d personally be worried about migrating, just re-fetch. Sounds cleaner anyway?
Sorry I’m late to the party!
Oops, I think this pod (twtxt.net) just sync ~1k missing root twts with god only knows which peers 🤦♂️ I forgot a couple of important key things:
- Only coverage with a subset of peers
- Only converge with trusted peers
Fuck me 🤣 Ooops. Sorry!
@movq@www.uninformativ.de no no it’s ok i say it because it’s true also it’s funny to me hahah! don’t be sorry
@kat@yarn.girlonthemoon.xyz Ouch. 🥴 Alright, that’s not so great then, sorry. 🫣🥴
@thecanine@twtxt.net I’m so sorry I fucked things up 🥲 I hope you can trust I’ll try to do a better job of backups and data going forward 🤗
@bender@twtxt.net Sorry to disappoint (again): https://blogs.nasa.gov/planetarydefense/2025/02/24/latest-calculations-conclude-asteroid-2024-yr4-now-poses-no-significant-threat-to-earth-in-2032-and-beyond/
@andros@twtxt.andros.dev yeah, sorry I couldn’t get back to you sooner. I’ve already made an account on codeberg in order to file in an issue but, I just can’t get myself to concentrate with everything going on with the family lately. I’ll do my best and get things done properly and soon
@sorenpeter@darch.dk Sorry, I realized that shortly after posting. Here’s another attempt to post the images:

