When washing the dishes at the scouts I cut my hand open on the ladle. That piece of shit has a terrible burr.

@prologic@twtxt.net Of course you don’t notice it when yarnd only shows at most the last n messages of a feed. As an example, check out mckinley’s message from 2023-01-09T22:42:37Z. It has “[Scheduled][Scheduled][Scheduled]“… in it. This text in square brackets is repeated numerous times. If you search his feed for closing square bracket followed by an opening square bracket (][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I’ve explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.

@movq@www.uninformativ.de Ja, völlig behämmert. Schade, vertane Chance für einen „Doch“-Knopf.

Boah, jetzt mal ernsthaft, was ist denn das für ein Dialog bittesehr!?

Image

Wer hat sich zu dieser Meldung diese Knopfauswahl überlegt und dann auch noch die Icons dazu ausgedacht? Und warum hat’s das Zertifikat überhaupt schon wieder zerlegt? Und wieso kommt der Dialog direkt wieder in ner Endlosschleife hoch, wenn ich abbreche? Komplettversagen nach Strich und Faden an allen Enden. Allen. Grrr, so viel Hass! Ich schalt besser die Büchse aus.

@prologic@twtxt.net Tolerant yes, but in the right places. This is just encouraging people to not properly care. The extreme end is HTML where parsers basically accept any input. I’m not a fan of that. Whatever.

@prologic@twtxt.net The issue is that all bracketed text in the entire feed has been duplicated again two days ago. The bug is not fixed. Or it’s a new one.

@movq@www.uninformativ.de I can relate to that. :-/

@andros@twtxt.andros.dev I suggest to not touch it and work on a different project instead. :-D

No, in all seriousness, that’s a tough one. Try to figure out the requirements and write tests to cover them. In my experience, if there is no good documention, tests might also be lacking. It goes without saying that you have to understand the code segments first before you can begin to refactor them. Commit even earlier and more often than usual, this will help you bisecting potentially introduced bugs later on. Basically baby steps.

But it also depends on the amount of refactoring required. Maybe just scrap it entirely and start from scratch. This might not be feasible due to e.g. the overall project size, though.

@andros@twtxt.andros.dev I’m all for elegant solutions. I prefer when the computer helps me to really achieve my goal and solve it completely, not where I still have to manually filter a list by hand. Anyway. :-)

@eapl.me@eapl.me Yeah, you need some kind of storage for that. But chances are that there’s already a cache in place. Ideally, the client remembers etags or last modified timestamps in order to reduce unnecessary network traffic when fetching feeds over HTTP(S).

A newsreader without read flags would be totally useless to me. But I also do not subscribe to fire hose feeds, so maybe that’s a different story with these. I don’t know.

To me, filtering read messages out and only showing new messages is the obvious solution. No need for notifications in my opinion.

There are different approaches with read flags. Personally, I like to explicitly mark messages read or unread. This way, I can think about something and easily come back later to reply. Of course, marking messages read could also happen automatically. All decent mail clients I’ve used in my life offered even more advanced features, like delayed automatic marking.

All I can say is that I’m super happy with that for years. It works absolutely great for me. The only downside is that I see heaps of new, despite years old messages when a bug causes a feed to be incorrectly updated (https://twtxt.net/twt/tnsuifa). ;-)

Hahahaha, this is brilliant! :‘-D https://denmarkification.com/

Exactly, @bender@twtxt.net, just like yours and prologic’s, too. :-( Subsequent Brackets Considered Harmful™.

@eapl.me@eapl.me Read flags are so simple, yet powerful in my opinion. I really don’t understand why this is not a thing in most twtxt clients. It’s completely natural in e-mail programs and feed readers, but it hasn’t made the jump over to this domain.

@mckinley@twtxt.net Yeah, all this JS and HTMX garbage messes up a lot of things which used to work better in the earlier days.

@prologic@twtxt.net @xuu There:

Image

Just search for ][ in https://twtxt.net/user/mckinley/twtxt.txt and you’ll see.

@movq@www.uninformativ.de @prologic@twtxt.net @bmallred@staystrong.run @andros@twtxt.andros.dev Thank you all! I don’t have emacs installed, so I’ll try lagrange and see. According to my shell history, I must have played around with amfora ages ago.

@xuu People should just fix their feeds. :-)

@movq@www.uninformativ.de Yeah, maybe. What browsers are you using again for these two?

I should really fix my calender rendering. A two day event only pops up in the first day, but not in the second. When extended to three days, it correctly shows up in all three days. Meh.

@mckinley@twtxt.net And there is the bracketed text duplication bug again… Actually with lots of twts. Did you edit a twt? Do you remember? /cc @prologic@twtxt.net

@mckinley@twtxt.net b

@bmallred@staystrong.run Surprisingly, my

User-agent: *
Disallow: /

seems to work. Or maybe those bastards change their user agent and claim to be someone nice. In any case, I just added a bunch of

location = /robots.txt {
    add_header Content-Type text/plain;
    return 200 "User-agent: *\nDisallow: /\n";
}

in my nginx config. No need for any bot to visit, crawl and index most of my sites.

@movq@www.uninformativ.de Photographic memory, eh?

@movq@www.uninformativ.de I also thought that I have a new Linux friend the other day. But it was just a fake KDE look from Redmond. :-(

@jost@jost.sdfeu.org Yeah, this AI crap is a big reason not to blog.

@movq@www.uninformativ.de So they say. :-D

I’m not a huge fan of docker. Sorry for the poor screen grab quality, but this is the funniest analogy for “no docker” vs “docker” I’ve come across: https://lyse.isobeef.org/tmp/no-docker-vs-docker-analogy.png :-D

Well, that’s another bug: The search https://twtxt.net/search?q=%22LOOOOL%2C+great+programming+tutorial+music%22 yields the wrong hash. It should have been poyndha instead.

@thecanine@twtxt.net Lol… I just don’t change my default profile pictures. (Well, only when my teammates ask me to.)

@doesnm@doesnm.p.psf.lt Haha, that’s great! :-D

They fixed it. :-D https://www.youtube.com/watch?v=A8b7HFUXPqk

@thecanine@twtxt.net Some precious cloud space. Probably the Atlassian one.

How does one end up with an avatar of that weird size to begin with? :-D

@falsifian@www.falsifian.org Do you want me to reconfigure my nginx to look at the User-Agent in order to serve you a different file for the time being? ;-) Good luck with your paper!

@movq@www.uninformativ.de Open-plan offices are just a giant mistake. I’ve never seen a single working one where people can actually concentrate. Except when I was the first one around in the morning.

@prologic@twtxt.net @bender@twtxt.net Looks like something for /dev/null.

While I now have a somewhat working fix for it in yarnd (https://git.mills.io/yarnsocial/yarn/pulls/1232), I also have the feeling that I should fix literal formatting in lextwt as well. This also uncovered more bugs I believe: https://git.mills.io/yarnsocial/go-lextwt/pulls/28

But then there is also the question why the textarea is populated with @<url> in the first place rather than @<nick url> or yarnd’s own @nick@domain/@nick syntax. It indeed has to do something with whether I follow the mentioned feed or not.

Anyway, something to investigate for future Lyse or maybe @prologic@twtxt.net and/or @xuu. G’night!

Righto, must be some caching thing that’s going on, too. Now, with JS enabled and a feed that I follow, hitting “Reply” actually automatically enters @nick@domain in the textarea. Submitting it correctly writes “@in the feed. Let's dig…

@bender@twtxt.net @prologic@twtxt.net I can reproduce this locally, too. But it doesn’t matter if I follow the feed or not. With JS enabled, hitting “Reply” opens a textarea with @<url>. Submitting this writes @<domain url> instead of @<nick url> in the feed.

However, when I have JS disabled, “Reply” jumps to the top of the page, but the the textarea is at the bottom. So, after scrolling down, the textarea is not filled with anything. Which is expected I reckon. Entering @nick@domain or just @nick resolves to the correct @<nick url> in the feed.

@prologic@twtxt.net @movq@www.uninformativ.de I sadly agree.

@movq@www.uninformativ.de So true! Either I’m hanging around with my direct teammates socializing in person in a meeting room or some other workmates are making so much noise in the open-plan office that I cannot concentrate at all. In any case, completely unproductive. :-D Luckily, I very rarely have to go to the office.

My hike today started off with a nice great spotted woodpecker right after the town sign. The -1°C didn’t feel all that cold in the sun. Even on the flat, I had to open my jacket with the sun on my back. The biotope got dug over, that’s now looking really sad. And they also fell a few large chestnuts. Surprisingly, there was actually snow on the mountain. Not much, maybe around three centimeters at most. It was melting and falling down the trees, which looked really cool. I enjoyed it a lot: https://lyse.isobeef.org/waldspaziergang-2025-02-04/

Image

@bender@twtxt.net Bwhahahahaaaahaaaahaaaaahaaaaaaa! :-D Oh man, my cheeks are hurting and eyes are watering. :-D I love it!

@falsifian@www.falsifian.org Yes! The first part about the history was my favorite. Not that the second one about finding life on Mars wasn’t interesting, no, not at all! But maybe it’s just that Earth is a bit more relatable. :-) I’m sure they will dig up something eventually.

@eapl.me@eapl.me Hahahahaa, this is truly brilliant! :-D The file descriptor slider is funny as heck! :-D

@movq@www.uninformativ.de The light pollution map reports red for my town. That’s fairly accurate, I’d say. The view from home is not all that great. Yeah, I can see Ursa Major and a bunch of other stars. Maybe even some satellites. But there’s definitely a sky glow at the horizon.

When I leave town, I can see a bit more. However, it doesn’t compare to the alps or even some rural parts in Australia. The latter was by far the craziest I’ve ever seen in my life. Looked like a space telescope photo in person. Soooooooooooooo many stars and the band of the milky way was easily visible to the naked eye. Up until then, I didn’t even know this was remotely possible down on earth. Absolutely stunning. :-)

@sorenpeter@darch.dk It depends on your requirements. If you just want to put your code somewhere for yourself, simply push it over SSH on a server and call it good. That’s what I do with lots of repos. If you want an additional web UI for read access for the public, cgit comes to mind (a mate uses that). Prologic runs Gitea, which offers heaps more functionality like merge requests.

That was a super interesting talk, I can recommend it: https://media.ccc.de/v/38c3-microbes-vs-mars-a-hacker-s-guide-to-finding-alien-life

@prologic@twtxt.net Go just moved back to second place. :-)

@movq@www.uninformativ.de Nice! I would have missed the plane if you hadn’t pointed it out. :-) Venus is very visible these days. When a mate and I went on a night walk during clear sky this week, the night sky looked really great, it was easy to spot the second planet. We got lucky, ISS just passed above our heads, too. Most of the week, it was cloudy, though.

@movq@www.uninformativ.de Hahaha, that’s a good one! :-D I came across this one before, but couldn’t remember the answer.

@prologic@twtxt.net Yes, C has it. I even thought that C invented it, but it seems to stem from CPL.

The closest to get to if expressions at the moment is to use a lambda:

foo := func() {
    if bar {
        return "spam"
    }
    return "eggs"
}()

But that’s also not elegant at all.

@arne@uplegger.eu Auweia! Wär’s da nicht sinnvoller, von dem Ding möglichst zügig wegzukommen? Ich hab keine Ahnung, was es da heutzutage so an tauglichen Alternativen gibt. Aber selbst alles selber zu bauen, wär da ja mittelfristig weniger aufwändig, wenn man das mit dem ständigen Zusammenkehren der Scherbenhaufen vergleicht.

@thecanine@twtxt.net That’s one of the cool properties, you can use it at whatever frequency you like.

@aelaraji@aelaraji.com :-D

@arne@uplegger.eu Jepp, sehr gute Wahl! :-)

@xuu I think I also ran into CSRF problems with multiple open yarnd tabs in the past.

@xuu Ah, it was JS then. Thanks. :-)

@movq@www.uninformativ.de Okay, cool. :-) I’ll look at Mutt this year. I have the feeling I might like it after some initial pain.

@movq@www.uninformativ.de Fingers crossed! :-)

@thecanine@twtxt.net It’s always nice to look at your creations.

Oh yeah, @aelaraji@aelaraji.com, electrostatic cat fur to the rescue! :-D

@prologic@twtxt.net Which one? I don’t mind the ternary operator at all. In fact, I often find myself missing it in Go. I don’t find the two alternatives particularly elegant:

foo := "eggs"
if bar {
    foo = "spam"
}

Or:

var foo string
if bar {
    foo = "spam"
} else {
    foo = "eggs"
}

To my eye, this just would look a lot nicer:

foo := bar ? "spam" : "eggs"

Or at least as the Pythons do it:

foo = "spam" if bar else "eggs"

The ternary operator especially shines with relatively short expressions.

@arne@uplegger.eu Ohjemine, TYPO3! O_o Lass mich schreiend davonlaufen!

Mit dieser absoluten Katastrophensoftware vor dem Herrn haben wir mal ein Studienprojekt gemacht. Die hat alle Vorurteile komplett übererfüllt. Angefangen von Fehlerseiten, die statt 4xx oder dergleichen immer mit HTTP 200 ausgeliefert wurden oder auch, dass das generierte HTML leider einfach ungültig war. Über die Implementierung von Löschen durch einen Deleted-Schalter in der Datenbank, das Speichern von Passwörtern im Klartext bis hin zu völlig umständlichen Bedienungskonzepten. Alles hat immer brutal viele Schritte gebraucht. Das Zeilennummernrumgeeier im TYPO-Script erinnerte eher an Basic. Uns kam es auch so vor, als ob man damit nicht ernsthaft was sinnvolles machen könnte.

Zu allem Überfluss hatte irgendwer noch ein ganz hundsmiserables Buch ausgegraben, das als Vorbereitung dienen sollte. Ich kann mich zum Glück weder an den Titel noch den Autor erinnern, aber ich weiß noch, wie das komplett inkonsistent geschrieben war. Anfangs gabs mehrere Seiten zu Unicode und UTF-8 wurde angepriesen, aber alle Beispiele haben dann auf ISO-8859-1 gesetzt. Gezeigter Beispielcode war häufig unterste Schublade. Selten hab ich so merkwürdige Erklärungen gelesen: „Wenn Sie die Sicherheitswarnhinweise stören, kommentieren Sie doch bitte im Quelltext die die()-Funktion in $ZEILE aus.“ Oder ein anderer Klassiker: „Ausgeschrieben würde der Code wohl folgendes tun…“. War sich der Autor also nicht ganz sicher, ob sein Codeschnipsel vllt. doch in Wahrheit was ganz anderes tut.

Seit diesem gigantischen Trauma (das hat mich wirklich sehr nachhaltig geprägt, wie man Dinge nicht machen sollte) hab ich erfolgreich einen Bogen um das TYPO3-Universum gemacht.

Ich kann nur hoffen, dass es zwischenzeitlich ein wenig besser geworden ist. Aber Deinem Kurzbericht zufolge scheint da ja immer noch der Wurm drin zu sein. Mein Beileid! :-(

@movq@www.uninformativ.de That’s an interesting setup! What MUA do you use?

@movq@www.uninformativ.de So, the building renovation finally started?

Rats! @aelaraji@aelaraji.com, you need an emergency hamster and a wheel attached to a bicycle dynamo…

Fingers crossed that this doesn’t happen a third time today.

If people just wrote error free code to begin with, there would be no need for error handling! :-P

No, honestly, I don’t think that there is anything wrong with the current approach. I don’t see any wins of any of the proposals I’ve come across.

@arne@uplegger.eu Hahaha! :-D

@kat@yarn.girlonthemoon.xyz You mean the ? as suffix for boolean returning functions or as ternary operator (condition ? true_value : false_value)?

Interestingly, I just had to look up the first case. I was under the wrong impression that the question mark at the end would be some shortcut for chained function or method calls that handles nil return values in a graceful way without actually dereferencing and thus crashing. I probably never wrote more than 30 lines of Ruby in my entire life. Must have been some other language.

@kat@yarn.girlonthemoon.xyz Haha, I see. :-)

Even after fixing yesterday’s mail server TLS certificate renewal incident (main hostname was not included) my KMail did not want to receive e-mails anymore. I had to restart Akonadi now in order to make this work again. I really should look at mutt one day.

@arne@uplegger.eu Eis im Januar, ja sapperlott, ist denn schon wieder Sommer im hohen Norden!?

@kat@yarn.girlonthemoon.xyz Something is broken with the TLS:

$ curl https://remix.girlonthemoon.xyz
curl: (35) error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error

@prologic@twtxt.net I don’t like it either. Too much magic, that only works in certain cases.

@movq@www.uninformativ.de No, I don’t think so. But I just looked it up. And yes, that sounds a bit creepy. I certainly heard similar calls, maybe it even was a heron. I don’t know.

That’s a cool comparision of an obstacle run with a knight, fire fighter and soldier: https://www.youtube.com/watch?v=pAzI1UvlQqw

@sorenpeter@darch.dk Thanks mate, I got really lucky with this one. :-)

@prologic@twtxt.net Have you successfully dug up some gold already? The dream of having your own yacht is coming closer.

@arne@uplegger.eu Ich gratuliere zum Vorhangstangenrichtfest. :-)

@arne@uplegger.eu Hehe, schon faszinierend, wie manche Sachen das Hirn ziemlich neu verdrahten.

@arne@uplegger.eu Zum Thema Dinosauerier fällt mir dieser 38C3-Vortrag ein, den ich mir die Tage angesehen hab: https://media.ccc.de/v/38c3-how-to-spec-fun-with-dinosaurs

I just saw this heron fly by my window, so I investigated: https://lyse.isobeef.org/graureiher-2025-01-25/

Image

@movq@www.uninformativ.de Es kann nun noch mehr Daten abschnorcheln! Hurra!

Thanks, @andros@twtxt.andros.dev! I commented and replied here: https://git.mills.io/yarnsocial/twtxt.dev/pulls/8#issuecomment-18490

@andros@twtxt.andros.dev Just when you have made something idiot-proof, the world invents a better idiot.

The mother of the morons is always pregnant.

@movq@www.uninformativ.de Progress! They could be at your door any second now. ;-)

@movq@www.uninformativ.de That’s cool! :-)

@xuu I’m innocent!

@movq@www.uninformativ.de Have the workers even arrived yet?

@arne@uplegger.eu Unzählige Stellschrauben hab ich auch noch vor mir. Ich will gar nicht dran denken. :-D

@arne@uplegger.eu Uuuuhhh, das fühlt sich klasse an, gute Arbeit mein Lieber! :-)

Besonders positiv hervorheben muss ich die Rohdatenansicht. Sowas hab ich mir auch schon in der Vergangenheit hin und wieder gewünscht. Wie toll es doch wär, direkt den Eintrag im Original zu sehen, ohne erst im Feed mühsam auf die Suche gehen zu müssen, was auch noch einen Wechsel auf den Browser oder den Editor erzwingt. Das werd ich mir definitiv auch einbauen. Insbesondere für die Entwicklung absolut hilfreich. Die Textarea könntest Du noch mit einem readonly-Attribut ausstatten.

Die Gesamtbaumansicht einer Unterhaltung gefällt mir ebenfalls. Davon bin ich ja ein großer Verfechter. Nicht nur die direkten Antworten zu sehen, sondern alle. Klar, bei tief verschachtelten Unterhaltungen und sehr langen Beiträgen verliert man da doch mal den Überblick, aber die kommen in der Praxis meiner Erfahrung nur selten vor.

Die zwei Elemente in der Fußzeile eines Beitrags würde ich auch noch versuchen in die Kopfzeile zu verschieben, dann wird die Darstellung insgesamt kompakter, gerade bei Unterhaltungen könnte das von Vorteil sein.

Weiter so!

@arne@uplegger.eu Klingt gut, Du darfst uns gern mal ein paar Bildschirmfotos vom aktuellen Stand zeigen. :-) Die erste Aufnahme sah bereits recht aufgeräumt aus.

Ich müsste auch endlich mal an meinem Client weitermachen. Aber heut nimmer.

@arne@uplegger.eu Ahja, danke für die Erläuterung! Einrückungen waren meinem Parser tatsächlich egal, der dürfte einfach ein trim() angewendet haben, bevor sich die Zeile zur näheren Verarbeitung angesehen hat. :-D

@movq@www.uninformativ.de It says F=700, D=70 and RK=20. I have to research what magnification that translates to, a few days have passed since physics class. Your Celestron Ultima 100 looks much more high quality than this thing.

@movq@www.uninformativ.de Großartig! :-D

@arne@uplegger.eu Hahaha, vor Dekaden hab ich auch mal einen „XML“-„Parser“ selbst gebaut. Der wollte dann pro Zeile entweder einen öffnenden oder einen schließenden Tag oder aber einen Wert haben. :-O Ganz übel, aber für den damaligen Anwendungsfall hat’s gelangt. War halt bloß kein XML. :-D

Was konkret war dann das Problem von dem zu sauberen XML in Deinem Fall? Und schön zu hören, dass Du das Gerät vor dem vorzeitigen Elektroschrotttod bewahrt bekommen hast. :-)

Zum Abschluss noch ne ganz doofe Frage, ganz offensichtlich hab ich von Radios keinen blassen Schimmer. Wieso muss denn das Ding überhaupt mit XML rumfuhrwerken? O_o

@xuu The Pod.LastSeen and Pod.LastUpdated fields are only ever updated in the Cache.DetectPodFromUserAgent(…) function as far as I can tell. This function is called in Cache.DetectClientFromRequest(…) and Cache.DetectClientFromResponse(…).

Cache.DetectClientFromRequest(…) is only invoked when the twtxt.txt is requested and looks at the User-Agent HTTP request header.

Cache.DetectClientFromResponse(…) is only called in Cache.FetchFeeds(…) and looks at the Powered-By HTTP response header. This header would be set in twtxt.txt HTTP responses from yarnd. A bunch of places invoke Cache.FetchFeeds(…), including a periodic job (UpdateFeedsJob.Run()). Maybe something is iffy around these locations.

@movq@www.uninformativ.de It’s an old, cheap Optus without any model information on it. It was maybe 180DM or so in a discounter 25, 30 years ago. Its main job is to collect dust, can’t even remember its last use. That must have been easily 15 years ago I reckon. Thus, absolutely no surprise. Maybe I’ll just take it apart and see what I can see as the week progresses.

I’m rather frozen after half an hour looking at Venus and Saturn through the telescope outside. I couldn’t see any rings around Saturn. Disappointing. It also appeared rather dark. The very bright Venus on the other hand told me that there is something growing inside the scope. :-( Or maybe there is dust.

@xuu I added some logging when a “dead” peer is removed as I suspect this to be a hot candidate for all the trouble. https://git.mills.io/yarnsocial/yarn/commit/21538951f9dc71b9366db6dbb784a8078096a4c8 Does this yield anything?