@aelaraji@aelaraji.com As long as you’re having fun, you’re doing the right thing. 😅 (Kind of. 😂)
@lyse@lyse.isobeef.org Now I feel like an ant. 🐜 (Imagine how ants must feel when they see this! 🤯)
text file busy. Example:
@bender@twtxt.net Consider me stumped! 😅 Yeah, I can imagine this not being super fast. 🥴
text file busy. Example:
@movq@www.uninformativ.de allow me to stump you! Our Oracle team runs scripts, java, and a few others from NFS shares. That has become a true problem when VMs have moved to Azure, and NFS servers remain on premises. NFS doesn’t like latency, especially when laced with high I/O activity.
@prologic@twtxt.net right, but “regular” forks have parents. An edited twt—currently—has none. Edits just create a new branch-less leaf.
text file busy. Example:
I guess crashing the program with a SIGBUS is intentional. Here’s a blog post that describes this exact thing when running binaries off of NFS:
https://rachelbythebay.com/w/2018/03/15/core/
It’s just that this also happens locally nowadays and, thus, much easier and more often (I bet few people run programs via NFS these days). 🫤
Not a fan of this. (Time will tell if I have the energy to discuss this on the Linux kernel mailing list.)
text file busy. Example:
@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.
@slashdot@feeds.twtxt.net wut da fuq?! What happened? What da hell was the Australian federal police even doing or asking? da fuq? I didn’t even know Session was based in Australia?! 🇦🇺 Oh my 😱 – I think this is worth enough to raise this with my local Federal MP (Elizabeth Watson Brown). This is nuts. The Australia FP can get bent 🤦♂️ I’d like to learn more about wtf happened here, seriously this is unacceptable and an overreach at first glance.
Encrypted Chat App ‘Session’ Leaves Australia After Visit From Police
Session, a small but increasingly popular encrypted messaging app, is moving its operations outside of Australia after the country’s federal law enforcement agency visited an employee’s residence and asked them questions about the app and a particular user. 404 Media reports: Now Session will be maintained by an entity in Switzerland. The mo … ⌘ Read more
@lyse@lyse.isobeef.org Oh man that was very sexy indeed 🤣 The detail! Oh my 😮
hop, entraînement terminé, j’ai fait le plein d’énergie avant d’aller donner un sang de qualitté ^^ #EFS #dondusang. Le niveau 7 de la méthode #lafay est par contre trop longue, je n’ai pas assez de temps pour faire ça bien. Tant pis dans ce cas, retour à la n°6 et j’y ajouterai 1 exercice jusqu’à épuisement tiré au sort. Ou alors je ressort le #TRX, il faut qu eje trouve où l’accrocher. #sport #training
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
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@asquare@asquare.srht.site No need to apologise 😅 All very good points 👌
@asquare@asquare.srht.site This is absolutely true! 💯 However the natural behavior of editing a post is the same as forking. So from a community perspective, we’re actaully okay with how that works in reality. I think we’re all getting a bit too hung up on “exactness”. One of the things I think we’re finding hard to reconcile is the fine line between a decentralised ecosystem and distributed system.
I want it very much to remain decentralised. That means Content-based addressing makes sense, because you can have integrity about what a Twt Hash means. I don’t really mind if a thread gets forked because the OP was edited, that’s actually how forking works anyway 😅
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@prologic@twtxt.net With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won’t be the case if a person you’re following is joining a thread started by people you aren’t following after the first twt of that thread has already been modified. Or if you’re knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
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.
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@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 🤣
twtxt.net. Meaning that I finally have some kind of access to an archive of the aforementioned debate.
@asquare@asquare.srht.site correct 👌
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
It’s pretty hard to follow though, with the discussion being spread out over so many threads and with the https://search.twtxt.net UI displaying threads in a way that’s different than how https://twtxt.net does.
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
I finally figured out that https://search.twtxt.net is not the same as https://twtxt.net/search. The former is open to the general public, unlike the latter which is only for registered users of twtxt.net. Meaning that I finally have some kind of access to an archive of the aforementioned debate.
performed a small, screen-based update to jarotsim, for it to run better in smaller and bigger screens | https://compudanzas.net/jarotsim.html
I’m not even supposed to do be doing any of this, I should be making stuff* with Shapes, forms and color instead of poking at software with a stick like a caveman. 😆
*Stuff: Things I make and refuse to call Art, unless I have to in a resume and what not.
@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.
text file busy. Example:
I guess the question now becomes;
Why does it cause the running process to crash?
text file busy. Example:
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. 🤦
text file busy. Example:
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.
text file busy. Example:
It’s intentional:
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.
text file busy. Example:
@movq@www.uninformativ.de Sounds like you’ll be submitting a bug report upstream though at some point when you have time? 🤔
text file busy. Example:
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. 🫤
text file busy. Example:
@prologic@twtxt.net I haven’t narrowed it down yet. I’m running 6.11.4 at the moment.
text file busy. Example:
@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. 😢
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@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.
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
@asquare@asquare.srht.site Yeah we know 🤣 Still debating changes to the extension 😅
So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash – 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
Yeah I know! My ship was sinking and I’ve just noticed. Patched up the holes and now we’re back afloat.
@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
gg=G and to va", ci", di{... in vim the other day 😆 Life will never be the same, I can feel it. ref
@bmallred@staystrong.run I always get to imagine vim with its roots from vi and ed
@asquare@asquare.srht.site Hehw 🤣
@asquare@asquare.srht.site This is true! Even true of the extensions 👌
hut publish, "publicise my user agent" with manual curl invocations (when I remember to) (thanks to @movq for the informative guide https://www.uninformativ.de/twtxt-mention.html), and as for following other people's feeds, I still haven't decided how I'm going to do that.
@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 🤣