# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 196262
# self = https://watcher.sour.is?offset=173856
# next = https://watcher.sour.is?offset=173956
# prev = https://watcher.sour.is?offset=173756
[47°09′42″S, 126°43′25″W] --bad checksum--
LMAO!!! The bitreich landing page is hilarious 😂
> "... we only store good cake recipes, this complies with the GCPR - _General Cookie Protection Ruling_"
LMAO!!! The bitreich landing page is hilarious 😂
> "... we only store good cake recipes, this complies with the GCPR - _General Cookie Protection Ruling_"
LMAO!!! The bitreich landing page is hilarious 😂
> "... we only store good cake recipes, this complies with the GCPR - _General Cookie Protection Ruling_"
🧮 USERS:1 FEEDS:2 TWTS:1130 ARCHIVED:80010 CACHE:2452 FOLLOWERS:17 FOLLOWING:14
[47°09′43″S, 126°43′06″W] 4204 days without news from Herve
Alas, I can't get myself to resist. Interacting with tech and software makes me feel like a kid in a candy shop: "I wanna taste all of it! Find my favorite Lollipop and wonder about where it came from, who made it? How is it possible to turn any kind of mushy juicy fruit into a hard, forever lasting candy in a freaking stick!? Oh, Wait!! Is THAT chocolate over there!!?"
Alas, I can't get myself to resist. Interacting with tech and software makes me feel like a kid in a candy shop: "I wanna taste all of it! Find my favorite Lollipop and wonder about where it came from, who made it? How is it possible to turn any kind of mushy juicy fruit into a hard, forever lasting candy in a freaking stick!? Oh, Wait!! Is THAT chocolate over there!!?"
Alas, I can't get myself to resist. Interacting with tech and software makes me feel like a kid in a candy shop: "I wanna taste all of it! Find my favorite Lollipop and wonder about where it came from, who made it? How is it possible to turn any kind of mushy juicy fruit into a hard, forever lasting candy in a freaking stick!? Oh, Wait!! Is THAT chocolate over there!!?"
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._
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._
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 Although my recent breakage/down time was more of a result of human error than it is something to blame on software itself, I do get your point; and will highly probably end up going the same route in the near future. It's just that in order to south my forever itching curiosity, I have to learn and try some things first.
@movq Although my recent breakage/down time was more of a result of human error than it is something to blame on software itself, I do get your point; and will highly probably end up going the same route in the near future. It's just that in order to south my forever itching curiosity, I have to learn and try some things first.
@movq Although my recent breakage/down time was more of a result of human error than it is something to blame on software itself, I do get your point; and will highly probably end up going the same route in the near future. It's just that in order to south my forever itching curiosity, I have to learn and try some things first.
@movq 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.
[47°09′13″S, 126°43′07″W] Reading: 1.86000 PPM
I guess the question now becomes;
> Why does it cause the running process to crash?
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. 🤦
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. 🤦
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. 🤦
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.
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.
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.
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.
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.
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.
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 Sounds like you'll be submitting a bug report upstream though at some point when you have time? 🤔
@movq 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. 🫤
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. 🫤
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. 🫤
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 I haven’t narrowed it down yet. I’m running 6.11.4 at the moment.
@prologic I haven’t narrowed it down yet. I’m running 6.11.4 at the moment.
@prologic I haven’t narrowed it down yet. I’m running 6.11.4 at the moment.
@prologic I haven’t narrowed it down yet. I’m running 6.11.4 at the moment.
@movq Is this on a particular Kernel version? 🤔
@movq 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 …
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 …
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 …
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).
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).
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).
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 We always had the famous Kaffee und Kuchen around 4pm or even a bit later. 😅 Guess we’re not certified Germans. 😢
@lyse We always had the famous Kaffee und Kuchen around 4pm or even a bit later. 😅 Guess we’re not certified Germans. 😢
@lyse We always had the famous Kaffee und Kuchen around 4pm or even a bit later. 😅 Guess we’re not certified Germans. 😢
@lyse We always had the famous Kaffee und Kuchen around 4pm or even a bit later. 😅 Guess we’re not certified Germans. 😢
@asquare 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 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._
[47°09′56″S, 126°43′18″W] Reading: 0.04000 PPM
#MaradoWeekly #WeeklyRecord Week 43 
1 VIII 1944 WARSZAWA LAIBACH
#MaradoWeekly #WeeklyRecord Week 43 1 VIII 1944 WARSZAWA LAIBACH
[47°09′17″S, 126°43′20″W] --no signal--
@asquare Yeah we know 🤣 Still debating changes to the extension 😅
@asquare Yeah we know 🤣 Still debating changes to the extension 😅
[47°09′26″S, 126°43′21″W] Sample analyzing complete -- starting transfer
doing less things. doing things well.
@asquare Hi back at you!! 👋 and nice to meet you!
@asquare Hi back at you!! 👋 and nice to meet you!
@asquare Hi back at you!! 👋 and nice to meet you!
🧮 USERS:1 FEEDS:2 TWTS:1129 ARCHIVED:79995 CACHE:2445 FOLLOWERS:17 FOLLOWING:14
I believe it's about time I learned to use Treafik.
I believe it's about time I learned to use Treafik.
I believe it's about time I learned to use Treafik.
Yeah I know! My ship was sinking and I've just noticed. Patched up the holes and now we're back afloat.
Yeah I know! My ship was sinking and I've just noticed. Patched up the holes and now we're back afloat.
Yeah I know! My ship was sinking and I've just noticed. Patched up the holes and now we're back afloat.
[47°09′14″S, 126°43′08″W] Raw reading: 0x67155331, offset +/-4
@movq 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 We are just a terrible species. :-(
I found Timeline by @sorenpeter and I liked it. Decided to change some stuff around. Making some nice progess on my version of Timeline 
[47°09′03″S, 126°43′47″W] --interrupted--
Dois anos após a implementação de medidas de proteção integral na Reserva Natural das Ilhas Selvagens, surge uma inaceitável tentativa de reabrir a pesca nesta área. A proposta apresentada à Assembleia Legislativa da Madeira pretende reduzir a zona de proteção de 12 para 2 milhas náuticas, permitindo a captura de atuns, o que coloca em risco os compromissos de conservação que posicionaram a Madeira como referência internacional na defesa dos ecossistemas marinhos.
Uma proposta do partido CHEGA Madeira pretende reverter a proteção total do maior santuário marinho da Europa – e não podemos permitir este retrocesso!
Proteja as Ilhas Selvagens – participe nesta ação!
https://atum.zero.ong/
Dois anos após a implementação de medidas de proteção integral na Reserva Natural das Ilhas Selvagens, surge uma inaceitável tentativa de reabrir a pesca nesta área. A proposta apresentada à Assembleia Legislativa da Madeira pretende reduzir a zona de proteção de 12 para 2 milhas náuticas, permitindo a captura de atuns, o que coloca em risco os compromissos de conservação que posicionaram a Madeira como referência internacional na defesa dos ecossistemas marinhos.
Uma proposta do partido CHEGA Madeira pretende reverter a proteção total do maior santuário marinho da Europa – e não podemos permitir este retrocesso!
Proteja as Ilhas Selvagens – participe nesta ação!
https://atum.zero.ong/
@bmallred I always get to imagine vim with its roots from vi and ed
@bmallred I always get to imagine vim with its roots from vi and ed
@movq I didn't realize elves were considered malicious either.