In any case, yes Content addressing can break threads when the original content is edited that’s for sure, however we’ve since agreed and realized that technically speaking, we can actually identify from a clients perspective, whether an edit took place.

@asquare@asquare.srht.site Iant yhay what I said? Or did I fat-finger my reply 🤣

@asquare@asquare.srht.site Yeah my UI skillz aren’t so great sorry 🤣

@asquare@asquare.srht.site correct 👌

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

I guess the question now becomes;

Why does it cause the running process to crash?

Just tried it: It did indeed crash my Wayland session and, since Wayland compositors are sensitive and critical, it froze all input devices. Only way to recover was to SSH into that machine and reboot it. 🤦

Not sure I’m happy with this.

Take this, for example:

https://codeberg.org/dwl/dwl/src/branch/main/Makefile#L64

The install target of a Wayland compositor uses cp to copy the compiled binary to your bin directory. So, as of Linux 6.11, when you recompile this compositor and reinstall it, it will crash your entire Wayland session. 🧟💀🧟

One way to avoid this crash is to use install instead of cp. install calls unlink() before copying the data, thus avoiding this situation entirely. Not all Makefiles do that, though.

It’s intentional:

• https://lwn.net/Articles/982034/
  
• https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a010c412853
  

Matching the behavior of most Unix systems, the Linux kernel has traditionally prevented writes to an executable file that is in use by a process somewhere in the system; that is the source of the “text file busy” message that some readers may have seen. This restriction is intended to prevent unpleasant surprises in running programs. Kernel developers have been phasing out this restriction for a few years, mostly because it does not really protect anything. As of 6.11, the kernel will no longer prevent writes to busy executable files; see this changelog for a lot more details.

Hm.

@movq@www.uninformativ.de Sounds like you’ll be submitting a bug report upstream though at some point when you have time? 🤔

This changed between linux-6.10.10.arch1-1 and linux-6.11.arch1-1 … Don’t have the time now to do a proper bisect. 🫤

@prologic@twtxt.net I haven’t narrowed it down yet. I’m running 6.11.4 at the moment.

@movq@www.uninformativ.de Is this on a particular Kernel version? 🤔

When you try to change a file that’s currently running, it used to say text file busy. Example:

First terminal:

$ cc -Wall -Wextra -o test test.c
$ cp test run
$ ./run

Second terminal:

$ cp test run
cp: cannot create regular file 'run': Text file busy

But on my machines today, it crashes the running program. 🤨 As soon as I run the cp, I get a coredump:

$ ./run
... time passes, I do "cp test run" in a second terminal ...
Bus error (core dumped)

How odd. Another mystery to solve …

You can pry OpenBSD’s httpd + acme-client from my cold dead hands. Set it up years ago and it never failed (unlike all the fancy stuff we tried at work).

@lyse@lyse.isobeef.org We always had the famous Kaffee und Kuchen around 4pm or even a bit later. 😅 Guess we’re not certified Germans. 😢

@asquare@asquare.srht.site We’ve collectively as a community (welcome to the community too! 🥳) had a many-week, multi-thread debate over this. It all boils down to Content Addressing vs. Location Addressing and the benefits, pros/cons of each approach. Ultimately though threads in Twtxt take advantage of a convention we formalized as the Twt Subject. This is combined with a Location-based Addressing, the Twt Hash extension. In the end we are likely to stay with this approach, but fix the parameters we use and truction.

@asquare@asquare.srht.site Yeah we know 🤣 Still debating changes to the extension 😅

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

This is so funny – and very true. 😃 The ancient German art of complaining: https://youtu.be/FcFmVfAg8V0?t=720

Good job, humans. 🙄 https://movq.de/v/ebebe2801a

@bmallred@staystrong.run I always get to imagine vim with its roots from vi and ed

@asquare@asquare.srht.site Hehw 🤣

https://twtxt.dev

@asquare@asquare.srht.site This is true! Even true of the extensions 👌

@asquare@asquare.srht.site So basically very manual? 🤔

@prologic@twtxt.net … I guess so, yeah 😂🤪

@movq@www.uninformativ.de Seems like a cool game 🤔 Hard to play on mobile though 🤣

Speaking of typing, do you know this game? https://zty.pe/

@aelaraji@aelaraji.com lol 😅 Not crazy fast. People in the office regularly surprise me with their fast typing. According to https://10fastfingers.com/typing-test/german, it’s around 90-ish WPM.

@prologic@twtxt.net I know that problem. 😃

@asquare@asquare.srht.site Ahh, so they did have eyes! We also have a couple of moorhens (among others) at our pond: https://movq.de/v/6732d85263/ Number 7 is an adolescent one.

The V: pattern itself is quite good because you can do quite a lot of powerful things with selected text.

For example: ggV}:s/^/ -/ will insert a - at the beginning of every line turning your bunch of lines into a Markdown list of items 😅

@movq@www.uninformativ.de Same here 🤣 My fingers know everything, my brain does not 😅 Same with passwords too, at least the important ones, master password, passwords for my machine(s) and work laptop. Don’t ever try to interrogate me for them, only my fingers know 🤣

@aelaraji@aelaraji.com … this made me realize that I don’t really know anymore which commands I use. It’s all muscle memory by now. 🤔

Offen Fair Web Analytics This looks pretty good., might give this a try. Been using GoatCounter, but it’s pretty bland in that it doesn’t really tell me much 😅

👋 Reminder folks of the upcoming Yarn.social monthly online meetup:

• Event: Yarn.social Online Meetup
  
• When: 26th October 2024 at 12:00PM UTC (midday)
  
• Where: Mills Meet : Yarn.social
  

#Yarn.social #Meetup

TIL: The word “eldritch”, as in “eldritch horror”, does not refer to some small village in England. 🥴 https://www.etymonline.com/word/eldritch

@lyse@lyse.isobeef.org the addressing of the “Bug Bounty program associated with this case” is such a total BS! I can’t help but believing the kid over Zendesk. The “-99” downvotes are telling. I could’t give mine, because I am not signing up on Zendesk for it. Ain’t nobody got time for that!

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.

@slashdot@feeds.twtxt.net seriously who the fuck is asking for this shit?

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

@slashdot@feeds.twtxt.net WHO does Tim Cook think he is anyway?! 🤦‍♂️

@aelaraji@aelaraji.com Noice 👌

@aelaraji@aelaraji.com And pray tell/share with us what these magical commands do? 🤣

@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

@bender@twtxt.net 🤣

Need more peeps in my clan. Anyone around playing Diablo IV? 😂