@movq@www.uninformativ.de In our case at work the new behavior can indeed be considered an improvement. systemd would then restart the new version automatically if the old one crashed. Still, crashing in the first place is very uncool. We don’t have a recent enough kernel version, though.

Heck yeah, this is some amazing space porn from ESA! https://dlmultimedia.esa.int/download/public/videos/2024/10/023/orig-2410_023_AR_EN.mp4

@movq@www.uninformativ.de My grandpa was very picky about the time and insisted on starting at 15:00 on time. Maybe that’s a Swabian thing, I don’t know.

@movq@www.uninformativ.de Nice!

@movq@www.uninformativ.de Kaffee und Kuchen erst um vier Uhr? Da sind die beiden aber ‘ne ganze Stunde zu spät dran! Und wie hebt sie denn das Messer, eieiei?!

Lol, Schnitzelklopfen mit einem in Tüte eingepackten Schlosserhammer, das kam mir so auch noch nie unter. :-D

“Like a true German, I’m going to open this beer with my eye socket.” Hahahahahahaaaaa! :-D

@movq@www.uninformativ.de We are just a terrible species. :-(

I thought I lost one of my knives at the flea market this year, but luckily, I just found it in my washbag. Woohoo, yippee! :-) So, I only miss the other that must have fallen out of my pocket when I cycled to the scouts last month.

@aelaraji@aelaraji.com Yeah, remebering them is a challenge. It often helped me in the past to just try using one or two new commands over and over again. But that obviously doesn’t work that well when the specialized command does not come up in daily routines all that often.

@aelaraji@aelaraji.com Nice tricks, ta! I actually came across di{ some time ago but entirely forgot about it.

@aelaraji@aelaraji.com Hahaha. :-D I saw some TLS errors today when fetching your feed. Welcome back. :-)

@prologic@twtxt.net @bender@twtxt.net A 15-year-old reported a security vulnerability in some shitware and they acted like absolute dickheads. Unfortunately, that’s how it often goes. The internet is full of similar reports where people a treated like that by companies, sometimes even way worse than that.

Read it, prologic, it’s totally worth it. That’s a great writeup by some very cool dude.

The PR article by the company just speaks for itself and reinforces their dick move. No more questions. https://support.zendesk.com/hc/en-us/articles/8187090244506-Email-user-verification-bug-bounty-report-retrospective

Haha, I love it! https://gist.github.com/hackermondev/68ec8ed145fcee49d2f5e2b9d2cf2e52

@movq@www.uninformativ.de Und nicht behebt. Schlag ich morgen mal unserem Auftraggeber vor. 8->

@movq@www.uninformativ.de Yup, I think that’s my favorite season.

I do not notice any lag with my Logitech Lift. Haven’t changed the inital battery from July last year yet. I have to say I’m rather impressed. The only reason for this cordless mouse is that I haven’t found a vertical mouse with a tail. Otherwise, I’d 100% taken that.

Autumn is there: https://lyse.isobeef.org/morgensonne-2024-10-11/

Image

@prologic@twtxt.net Bluetooth still classifies as connecting remotely. The attacker has to be in close proximity, but yeah. If you use it only where noone else is around, you’re fine. :-)

@prologic@twtxt.net I have no clue, but the only thing that comes to mind is that chances of RCE are higher the more it exposes.

Just to be clear, I’m 100% for mandating UTF-8 and only UTF-8. Nothing else. Exactly how it has always been.

I just like to send a proper Content-Type stating the right encoding to be a good web citizen. That’s all. :-)

Righto @anth@a.9srv.net, v2 is up again for me:

Clients (and human readers) just assume a flat threading
structure by default, read things in order […][…=]

I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn’t happen very often. Anyway, just a personal preference. Nothing to really worry.

The v2 spec requires each reply to re-calculate the hash
of the specific entry I’m replying to […][…=]

Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I’m probably just not getting your point here in the entire paragraph.)

Clients should not be expected to track conversations back
across forking points […][…=]

I agree. It totally depends on the client.

@movq@www.uninformativ.de If my memory serves me right, I think v2 doesn’t mention UTF-8 at all. Then I came along and noted that the Content-Type: text/plain might be not enough, as the HTTP spec defaults to Latin1 or whatever, not UTF-8. So there is a gap or room for incorrect interpretation. I could be wrong, but I understand @anth@a.9srv.net’s comment that he doesn’t want to even have a Content-Type header in the first place.

I reckon it should be optional, but when deciding to sending one, it should be Content-Type: text/plain; charset=utf-8. That also helps browsers pick up the right encoding right away without guessing wrong (basically always happens with Firefox here). That aids people who read raw feeds in browsers for debugging or what not. (I sometimes do that to decide if there is enough interesting content to follow the feed at hand.)

Merci, @movq@www.uninformativ.de! Back to gray this afternoon again, mostly dry, though.

Cool, @anth@a.9srv.net, thanks for the followup! I have to reread the original v2 in order to really follow your explanation, but that document seems to be offline at the moment. I’ll try again later. :-)

Oh no, @xuu@txt.sour.is. :-( Speedy recovery and I hope you still miss out on long-covid.

Ta, @prologic@twtxt.net!

Finally, a sunny day. I jumped at the opportunity and went for a quick evening stroll: https://lyse.isobeef.org/waldspaziergang-2024-10-09/

Image

Good luck and all the best wishes, @bender@twtxt.net. Please don’t die!

@movq@www.uninformativ.de That was indeed an interesting dive! I also never heard of just before.

LOL: http://gopher.quux.org:70/Humor%20and%20Fun/Microsoft_KSH.txt|/MBOX-MESSAGE/1