@prologic@twtxt.net hmm this isnt right..

@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

hmm interesting work here.. ill give it a look.. @lyse@lyse.isobeef.org do you know if it is even storing the url into the AST object? afair the code to parse tags url should be the same as the mention url.

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

@movq@www.uninformativ.de Schön mal noch eine Querreferenz zu haben. Danke!
Beide O-Maten haben ähnlich Ergebnisse für mich. Das bestätig mich in meiner bereits getroffenen Wahlentscheidung für den 23. Februar.

@arne@uplegger.eu Der Real-O-Mat ging neulich auch rum: https://real-o-mat.de/ (Ändert bei mir im Ergebnis nix, die Antworten/Begründungen sind aber interessant(er).)

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@txt.sour.is. G’night!

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

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

@twtxt.net@twtxt.net right. I don’t follow you. I will restart following you once Yarn has fixed this problem. :-P

@bender@twtxt.net Every base is base 10.

@lyse@lyse.isobeef.org Thanks for sharing. I really enjoyed it. The beginning part about the history of life on Earth was fun to watch having just read Dawkin’s old book The Selfish Geene, and now I want to read more about archaea. The end of the talk about what might be going on on Mars made me a bit hopeful someone will find some good evidence.

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

@twtxt.net@twtxt.net Octal 31 = Decimal 25

@johanbove@johanbove.info Ours also inlcudes the streaming portal https://www.filmfriend.de
It’s nice to watch some arthaus and off main stream movies.

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

@jost@jost.sdfeu.org Hello jost!

@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 I’m gonna give you a hint: Octal, decimal. 😅

@movq@www.uninformativ.de That is a good one! It took me 15 minutes to get it. 🤓

@movq@www.uninformativ.de Nice, at first my brain went assignment versus equality, but then after a sip of coffee I got it.

@prologic@twtxt.net Sorry to hear that.

@prologic@twtxt.net In the EU there are Laws, Rules and Regulations for many things. I’m not an expert, but your case may sound like it could match to the EU Digital Services Act.

[…] for example, the obligation to establish points of contact for authorities and citizens […]

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

@lyse@lyse.isobeef.org Es ist immer noch so ähnlich. Da kommen so viele verschiedene Ebenen innerhalb und außerhalb der TYPO3-Umgebung zusammen, dass man sich wundert.

Und die TYPO3-Core-Entwickler nehmen gefühlt jeden fancy Shice mit, den sie gerade finden. Das reißt dann immer wieder Prozesse ein oder es muss ein gigantischer Aufwand betrieben werden, damit “grundlegende” Funktionen wieder hergestellt werden.
In den Kommentaren ist dann immer nur zu lesen “Tja, Pech. Gibt’s nicht mehr. Sei froh, dass wir ‘ne undokumentierte Schnittstelle dazu im Code versteckt haben. Bau’s dir selbst.”
Und der OpenSource-Gedanke ist bei einigen Erweiterungen (die als Quasi-Standard gelten) auch nur noch zu erahnen. Da müssen teilweise Abos abgeschlossen werden, damit einige Funktionen genutzt werden können.

Es wird auf jeden Fall nie langweilig.

@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@txt.sour.is I think I also ran into CSRF problems with multiple open yarnd tabs in the past.

@xuu@txt.sour.is 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.

@lyse@lyse.isobeef.org The one in question is more like the javascript version for unwrapping errors when accessing methods.

 const value = some?.deeply?.nested?.object?.value

but for handling errors returned by methods. So if you wanted to chain a bunch of function calls together and if any error return immediately. It would be something like this:

b:= SomeAPIWithErrorsInAllCalls()
b.DoThing1() ?
b.DoThing2() ?

// Though its not in the threads I assume one could do like this to chain.
b.Chain1()?.Chain2()?.End()?

I am however infavor of having a sort of ternary ? in go.

PS. @prologic@twtxt.net for some reason this is eating my response without throwing an error :( I assume it has something to do with the CSRF. Can i not have multiple tabs open with yarn?

@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

@lyse@lyse.isobeef.org would it work wit cats instead? there has been a whole flock of them in the neighborhood the last couple of days, one female and a gazillion males taking turns 😅 … at least they’d be good for something other than their non-stop after midnight opera 😂

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