# 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 196302
# self = https://watcher.sour.is?offset=165438
# next = https://watcher.sour.is?offset=165538
# prev = https://watcher.sour.is?offset=165338
[47°09′32″S, 126°43′13″W] Transfer 25% complete...
@bender YES! They'll be sucking on a 1000GB Lollipop per request! 😂 I bet their VPS providers will be happy! *VERY* happy!
@bender YES! They'll be sucking on a 1000GB Lollipop per request! 😂 I bet their VPS providers will be happy! *VERY* happy!
@lyse Yeah, it’s super handy, right? Especially when copying text between terminals.

It looks like this protocol has been sitting in “unstable” for at least 5 years now:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main/unstable/primary-selection

Some months ago, they tried to move it (and others) to “staging”:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/252/diffs#46fa0a22de556f66f7cf1876c4c1817b65f886f5

And that’s where it is now.

I’m not sure what “unstable” actually means in this context, nor “staging”/“stable”. Is there someone actively working on this? How bad is it really if it just sits in “unstable” for years? What are the consequences of a move to “stable” – do clients need to be updated to request the new version? 🤔
@lyse Yeah, it’s super handy, right? Especially when copying text between terminals.

It looks like this protocol has been sitting in “unstable” for at least 5 years now:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main/unstable/primary-selection

Some months ago, they tried to move it (and others) to “staging”:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/252/diffs#46fa0a22de556f66f7cf1876c4c1817b65f886f5

And that’s where it is now.

I’m not sure what “unstable” actually means in this context, nor “staging”/“stable”. Is there someone actively working on this? How bad is it really if it just sits in “unstable” for years? What are the consequences of a move to “stable” – do clients need to be updated to request the new version? 🤔
@lyse Yeah, it’s super handy, right? Especially when copying text between terminals.

It looks like this protocol has been sitting in “unstable” for at least 5 years now:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main/unstable/primary-selection

Some months ago, they tried to move it (and others) to “staging”:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/252/diffs#46fa0a22de556f66f7cf1876c4c1817b65f886f5

And that’s where it is now.

I’m not sure what “unstable” actually means in this context, nor “staging”/“stable”. Is there someone actively working on this? How bad is it really if it just sits in “unstable” for years? What are the consequences of a move to “stable” – do clients need to be updated to request the new version? 🤔
@lyse Yeah, it’s super handy, right? Especially when copying text between terminals.

It looks like this protocol has been sitting in “unstable” for at least 5 years now:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main/unstable/primary-selection

Some months ago, they tried to move it (and others) to “staging”:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/252/diffs#46fa0a22de556f66f7cf1876c4c1817b65f886f5

And that’s where it is now.

I’m not sure what “unstable” actually means in this context, nor “staging”/“stable”. Is there someone actively working on this? How bad is it really if it just sits in “unstable” for years? What are the consequences of a move to “stable” – do clients need to be updated to request the new version? 🤔
@lyse Phew! 😅

It was just moist walls, luckily. Never happened before, as far as I can tell. Still, it’s a little disconcerting, yeah. 😅
@lyse Phew! 😅

It was just moist walls, luckily. Never happened before, as far as I can tell. Still, it’s a little disconcerting, yeah. 😅
@lyse Phew! 😅

It was just moist walls, luckily. Never happened before, as far as I can tell. Still, it’s a little disconcerting, yeah. 😅
@lyse Phew! 😅

It was just moist walls, luckily. Never happened before, as far as I can tell. Still, it’s a little disconcerting, yeah. 😅
>There is JavaScript, but not everything is implemented (properly). They’re writing everything including the JavaScript engine from scratch.

A huge effort 😲
@aelaraji is it candy, is it candy? Please tell me it is candy, pretty please! 😂
Eyes on logs... Waiting for the first s-kiddo to knock on my door. Got a *Huge* treat, just for them. \*wink\*
Eyes on logs... Waiting for the first s-kiddo to knock on my door. Got a *Huge* treat, just for them. \*wink\*
Eyes on logs... Waiting for the first s-kiddo to knock on my door. Got a *Huge* treat, just for them. \\*wink\\*
🧮 USERS:1 FEEDS:2 TWTS:1015 ARCHIVED:75561 CACHE:2359 FOLLOWERS:17 FOLLOWING:14
@mckinley Ahh I see!
@mckinley Ahh I see!
On my blog: Toots 🦣 from 06/24 to 06/28 https://john.colagioia.net/blog/2024/06/28/week.html #linkdump #mastodon #socialmedia #week
gopher://infinitelyremote.com Another Gopher fell down dead....
Thanks, @movq, it helped. :-) I'm happy to report it was just a quick storm, no water ingress.

Oh damn, water being pushed in through cracks in the walls? Holy crap! O_o That doesn't sound confidence-inspiring at all. How much water managed to get in? Any damages or just a moist floor/walls?
@movq I also do use both clipboards all the time. I can't live with just Ctrl+C/V. Select and middle click is sooooooooo handy. Despite I'm considering myself mostly a keyboard user.
[47°09′01″S, 126°43′36″W] Non-significative results -- sampling finished
Easy: 6.21 miles, 00:09:40 average pace, 01:00:06 duration
nothing to note. legs still feel good... a bit tired overall from a restless night.
#running #treadmill
Easy: 6.21 miles, 00:09:40 average pace, 01:00:06 duration
nothing to note. legs still feel good... a bit tired overall from a restless night.
#running #treadmill
Easy: 6.21 miles, 00:09:40 average pace, 01:00:06 duration
nothing to note. legs still feel good... a bit tired overall from a restless night.
#running #treadmill
(I’m not necessarily trying to rant *against* Wayland, btw. I just started using it more often lately, so I’m noticing more of the quirks. And I’m noticing all the little things that X11 did and that I used, and that now work differently on Wayland or not at all. Just trying to make sense of all of this and writing it down helps.)
(I’m not necessarily trying to rant *against* Wayland, btw. I just started using it more often lately, so I’m noticing more of the quirks. And I’m noticing all the little things that X11 did and that I used, and that now work differently on Wayland or not at all. Just trying to make sense of all of this and writing it down helps.)
(I’m not necessarily trying to rant *against* Wayland, btw. I just started using it more often lately, so I’m noticing more of the quirks. And I’m noticing all the little things that X11 did and that I used, and that now work differently on Wayland or not at all. Just trying to make sense of all of this and writing it down helps.)
(I’m not necessarily trying to rant *against* Wayland, btw. I just started using it more often lately, so I’m noticing more of the quirks. And I’m noticing all the little things that X11 did and that I used, and that now work differently on Wayland or not at all. Just trying to make sense of all of this and writing it down helps.)
@lyse Bah. 🫤 Well, fingers crossed. (It’s only going to get worse every year, though …)

I had some water in my apartment, too, last week. Different situation, it’s a tower building and I’m far away from ground level. We checked afterwards but we have no idea how that water got in. It was a heavy thunderstorm, so the theory is that the massive air pressure just pushed it in through tiny cracks somewhere …
@lyse Bah. 🫤 Well, fingers crossed. (It’s only going to get worse every year, though …)

I had some water in my apartment, too, last week. Different situation, it’s a tower building and I’m far away from ground level. We checked afterwards but we have no idea how that water got in. It was a heavy thunderstorm, so the theory is that the massive air pressure just pushed it in through tiny cracks somewhere …
@lyse Bah. 🫤 Well, fingers crossed. (It’s only going to get worse every year, though …)

I had some water in my apartment, too, last week. Different situation, it’s a tower building and I’m far away from ground level. We checked afterwards but we have no idea how that water got in. It was a heavy thunderstorm, so the theory is that the massive air pressure just pushed it in through tiny cracks somewhere …
@lyse Bah. 🫤 Well, fingers crossed. (It’s only going to get worse every year, though …)

I had some water in my apartment, too, last week. Different situation, it’s a tower building and I’m far away from ground level. We checked afterwards but we have no idea how that water got in. It was a heavy thunderstorm, so the theory is that the massive air pressure just pushed it in through tiny cracks somewhere …
So I’ve been wondering why some copy-and-paste actions “don’t work” on Wayland. Turns out, in Wayland there’s only one clipboard (like in probably most other OSes): The one where you select something and then hit ^C to copy it (it’s called the CLIPBOARD selection). They have intentionally not included the PRIMARY selection of X11 where you can just select some text to copy it and use the middle-mouse button to paste it.

Almost 10 years ago, they started an initiative to bring back PRIMARY:

https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection

That protocol is still “unstable” and thus not every Wayland client supports it:

https://wayland.app/protocols/primary-selection-unstable-v1

I honestly didn’t really look into this before and I didn’t know that it’s *still* unstable/unsupported, hence my confusion. (To be fair, I don’t know for certain if that particular protocol is already 10 years old. It looks like it because the copyright notice at the bottom says so, but no idea if that’s a reliable source.)

This is one of those things that are very subjective. The Wayland guys apparently thought that it was a “usability problem” to have two clipboards, so they removed one of them. Actually, the mechanism of X11 is totally generic, there are an “infinite” number of clipboards and we have just settled on using only two.

This is an interesting topic because Wayland is *so old* now that it looks like it has missed the developments of the last ~10 years or more: Way back in the past, I was indeed very confused about the different X11 clipboards because some clients used CLIPBOARD (hit ^C) and others only used PRIMARY (middle-mouse) – but this has long settled down. *Most* clients now have something like ^C to explicitly copy data into CLIPBOARD and ^V to paste it. It’s the standard thing now. And then *on top of that* power-users can additionally use PRIMARY where you just select text. This is a good and powerful thing, if you ask me.

I use both clipboards all the time. My mental model knows where the data goes. PRIMARY is like a short-term clipboard and CLIPBOARD is long-term. I think this is much better than just having one clipboard and I kind of feel like making good use of this is what keeps me from having to install a clipboard manager.~
So I’ve been wondering why some copy-and-paste actions “don’t work” on Wayland. Turns out, in Wayland there’s only one clipboard (like in probably most other OSes): The one where you select something and then hit ^C to copy it (it’s called the CLIPBOARD selection). They have intentionally not included the PRIMARY selection of X11 where you can just select some text to copy it and use the middle-mouse button to paste it.

Almost 10 years ago, they started an initiative to bring back PRIMARY:

https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection

That protocol is still “unstable” and thus not every Wayland client supports it:

https://wayland.app/protocols/primary-selection-unstable-v1

I honestly didn’t really look into this before and I didn’t know that it’s *still* unstable/unsupported, hence my confusion. (To be fair, I don’t know for certain if that particular protocol is already 10 years old. It looks like it because the copyright notice at the bottom says so, but no idea if that’s a reliable source.)

This is one of those things that are very subjective. The Wayland guys apparently thought that it was a “usability problem” to have two clipboards, so they removed one of them. Actually, the mechanism of X11 is totally generic, there are an “infinite” number of clipboards and we have just settled on using only two.

This is an interesting topic because Wayland is *so old* now that it looks like it has missed the developments of the last ~10 years or more: Way back in the past, I was indeed very confused about the different X11 clipboards because some clients used CLIPBOARD (hit ^C) and others only used PRIMARY (middle-mouse) – but this has long settled down. *Most* clients now have something like ^C to explicitly copy data into CLIPBOARD and ^V to paste it. It’s the standard thing now. And then *on top of that* power-users can additionally use PRIMARY where you just select text. This is a good and powerful thing, if you ask me.

I use both clipboards all the time. My mental model knows where the data goes. PRIMARY is like a short-term clipboard and CLIPBOARD is long-term. I think this is much better than just having one clipboard and I kind of feel like making good use of this is what keeps me from having to install a clipboard manager.~
So I’ve been wondering why some copy-and-paste actions “don’t work” on Wayland. Turns out, in Wayland there’s only one clipboard (like in probably most other OSes): The one where you select something and then hit ^C to copy it (it’s called the CLIPBOARD selection). They have intentionally not included the PRIMARY selection of X11 where you can just select some text to copy it and use the middle-mouse button to paste it.

Almost 10 years ago, they started an initiative to bring back PRIMARY:

https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection

That protocol is still “unstable” and thus not every Wayland client supports it:

https://wayland.app/protocols/primary-selection-unstable-v1

I honestly didn’t really look into this before and I didn’t know that it’s *still* unstable/unsupported, hence my confusion. (To be fair, I don’t know for certain if that particular protocol is already 10 years old. It looks like it because the copyright notice at the bottom says so, but no idea if that’s a reliable source.)

This is one of those things that are very subjective. The Wayland guys apparently thought that it was a “usability problem” to have two clipboards, so they removed one of them. Actually, the mechanism of X11 is totally generic, there are an “infinite” number of clipboards and we have just settled on using only two.

This is an interesting topic because Wayland is *so old* now that it looks like it has missed the developments of the last ~10 years or more: Way back in the past, I was indeed very confused about the different X11 clipboards because some clients used CLIPBOARD (hit ^C) and others only used PRIMARY (middle-mouse) – but this has long settled down. *Most* clients now have something like ^C to explicitly copy data into CLIPBOARD and ^V to paste it. It’s the standard thing now. And then *on top of that* power-users can additionally use PRIMARY where you just select text. This is a good and powerful thing, if you ask me.

I use both clipboards all the time. My mental model knows where the data goes. PRIMARY is like a short-term clipboard and CLIPBOARD is long-term. I think this is much better than just having one clipboard and I kind of feel like making good use of this is what keeps me from having to install a clipboard manager.~
So I’ve been wondering why some copy-and-paste actions “don’t work” on Wayland. Turns out, in Wayland there’s only one clipboard (like in probably most other OSes): The one where you select something and then hit ^C to copy it (it’s called the CLIPBOARD selection). They have intentionally not included the PRIMARY selection of X11 where you can just select some text to copy it and use the middle-mouse button to paste it.

Almost 10 years ago, they started an initiative to bring back PRIMARY:

https://wiki.gnome.org/Initiatives/Wayland/PrimarySelection

That protocol is still “unstable” and thus not every Wayland client supports it:

https://wayland.app/protocols/primary-selection-unstable-v1

I honestly didn’t really look into this before and I didn’t know that it’s *still* unstable/unsupported, hence my confusion. (To be fair, I don’t know for certain if that particular protocol is already 10 years old. It looks like it because the copyright notice at the bottom says so, but no idea if that’s a reliable source.)

This is one of those things that are very subjective. The Wayland guys apparently thought that it was a “usability problem” to have two clipboards, so they removed one of them. Actually, the mechanism of X11 is totally generic, there are an “infinite” number of clipboards and we have just settled on using only two.

This is an interesting topic because Wayland is *so old* now that it looks like it has missed the developments of the last ~10 years or more: Way back in the past, I was indeed very confused about the different X11 clipboards because some clients used CLIPBOARD (hit ^C) and others only used PRIMARY (middle-mouse) – but this has long settled down. *Most* clients now have something like ^C to explicitly copy data into CLIPBOARD and ^V to paste it. It’s the standard thing now. And then *on top of that* power-users can additionally use PRIMARY where you just select text. This is a good and powerful thing, if you ask me.

I use both clipboards all the time. My mental model knows where the data goes. PRIMARY is like a short-term clipboard and CLIPBOARD is long-term. I think this is much better than just having one clipboard and I kind of feel like making good use of this is what keeps me from having to install a clipboard manager.~
Earlier this week I found myself on the RIAA’s side in a legal dispute. Now I think Amy Coney Barrett got it right in her SCOTUS dissent. Truly we are in Bizarro World.
Earlier this week I found myself on the RIAA’s side in a legal dispute. Now I think Amy Coney Barrett got it right in her SCOTUS dissent. Truly we are in Bizarro World.
[47°09′13″S, 126°43′33″W] Analyzing samples
****
Por algo soy un solitario.. ⌘ Read more****
@movq The inlet has to be repaired. But I'm not gonna do that myself. You can imagine how easy it is to get tradesmen these days.

And here's the next thunderstorm lining up. Luckily, the rain barrel upgrade is completed. Also widened the funnel so that water running along the cable to the left is also caught. While typing, the rain gets stronger. Gotta check now. ;-)
@mckinley Whoop whoop. 🥳
@mckinley Whoop whoop. 🥳
@mckinley Whoop whoop. 🥳
@mckinley Whoop whoop. 🥳
@lyse Aarrrgh. 🙈🙈🙈 There’s nothing you can do to prevent that next time, is there?
@lyse Aarrrgh. 🙈🙈🙈 There’s nothing you can do to prevent that next time, is there?
@lyse Aarrrgh. 🙈🙈🙈 There’s nothing you can do to prevent that next time, is there?
@lyse Aarrrgh. 🙈🙈🙈 There’s nothing you can do to prevent that next time, is there?
[47°09′59″S, 126°43′40″W] Taking samples
The main thing is that nasty bugs or mosquitoes don't eat you.
[47°09′45″S, 126°43′00″W] --no signal--
@mckinley Is that because LadyBird doesn't have Javascript™? 🤔 There are _some_ things that don't currently degrade gracefully. We can improve things such that they do, just have to figure out what makes sense to degrade gracefully and what doesn't... 🤔
@mckinley Is that because LadyBird doesn't have Javascript™? 🤔 There are _some_ things that don't currently degrade gracefully. We can improve things such that they do, just have to figure out what makes sense to degrade gracefully and what doesn't... 🤔
[47°09′21″S, 126°43′59″W] --interrupted--
🧮 USERS:1 FEEDS:2 TWTS:1014 ARCHIVED:75547 CACHE:2361 FOLLOWERS:17 FOLLOWING:14
Summer here means you're sweating outside after a minute or two. lol.
On my blog: Real Life in Star Trek, Unification Part 1 https://john.colagioia.net/blog/2024/06/27/unification-part-1.html #scifi #startrek #closereading
Base: 9.24 miles, 00:09:45 average pace, 01:30:02 duration
just zoned out and watched some nightmare on elm street
#running #treadmill
Base: 9.24 miles, 00:09:45 average pace, 01:30:02 duration
just zoned out and watched some nightmare on elm street
#running #treadmill
Base: 9.24 miles, 00:09:45 average pace, 01:30:02 duration
just zoned out and watched some nightmare on elm street
#running #treadmill
Merci prx, j'utilise atom.awk modifié pour mon flux :-)
Merci prx, j'utilise atom.awk modifié pour mon flux :-)
It's about time to move while we still can! We had another heavy hail storm. 10-15mm diameter on average, maxing out at about 25mm. Oh boy. And my funnel contraption into the bucket at the cables in the basement were dead on.

[![Funnel into bucket](https://lyse.isobeef.org/tmp/wassertrichter-in-eimer/01-vorschau.jpg)](https://lyse.isobeef.org/tmp/wassertrichter-in-eimer/01.jpg)

Two larger streams were pouring out of the now porous looking mortar around the cables. Cool fountain in the basement. You would have thought that the right one was the bad one, but no, that one only dripped. I caught it just in time, not even half a minute later and the bucket would have spilled over. I estimate 60-75l water in total were about to mess up the floor again. Crisis averted.

[![Cables enter the house](https://lyse.isobeef.org/tmp/wassertrichter-in-eimer/02-vorschau.jpg)](https://lyse.isobeef.org/tmp/wassertrichter-in-eimer/02.jpg)

Gotta upgrade the bucket to a rain barrel until this is fixed.

Shortly after, I heared the fire brigade responding a couple of times.
[47°09′30″S, 126°43′27″W] Resetting dosimeter
@lyse Look forward to it 😅 Just gimme a few years to get past the "expensive school fees" and then we'll think about it 🤣
@lyse Look forward to it 😅 Just gimme a few years to get past the "expensive school fees" and then we'll think about it 🤣
[47°09′57″S, 126°43′03″W] Raw reading: 0x667D8C82, offset +/-5
But I get what you mean, too bad they're exinct 🤣
But I get what you mean, too bad they're exinct 🤣
@movq @prologic I'll join you at either place. :-)
@movq Oh that's hilarious! Your Twt didn't parsee and render properly! I _might_ have to think about switching to Goldmark 🤣


$ bat https://twtxt.net/twt/nmanhea | jq '.text'
"(#nhhbupa) @<prologic https://twtxt.net/user/prologic/twtxt.txt> Dunno, maybe you just love [Tasmanian devils](https://en.wikipedia.org/wiki/Tux_(mascot)#Tuz_2009)? 😅"
@movq Oh that's hilarious! Your Twt didn't parsee and render properly! I _might_ have to think about switching to Goldmark 🤣


$ bat https://twtxt.net/twt/nmanhea | jq '.text'
"(#nhhbupa) @<prologic https://twtxt.net/user/prologic/twtxt.txt> Dunno, maybe you just love [Tasmanian devils](https://en.wikipedia.org/wiki/Tux_(mascot)#Tuz_2009)? 😅"
@prologic Dunno, maybe you just love Tasmanian devils#Tuz_2009)? 😅
@prologic Dunno, maybe you just love Tasmanian devils#Tuz_2009)? 😅
@prologic Dunno, maybe you just love Tasmanian devils#Tuz_2009)? 😅
@prologic Dunno, maybe you just love Tasmanian devils#Tuz_2009)? 😅
@movq Why do you think I want to retire there 🤣
@movq Why do you think I want to retire there 🤣
@prologic 8.9 people per km², sounds awesome. 😃 Even less than Finland. 😅 (On average.)
@prologic 8.9 people per km², sounds awesome. 😃 Even less than Finland. 😅 (On average.)
@prologic 8.9 people per km², sounds awesome. 😃 Even less than Finland. 😅 (On average.)
@prologic 8.9 people per km², sounds awesome. 😃 Even less than Finland. 😅 (On average.)
@movq It's where I'd love to retire to 🤣
@movq It's where I'd love to retire to 🤣
@prologic I’d be fine with that, too. 😅
@prologic I’d be fine with that, too. 😅
@prologic I’d be fine with that, too. 😅
@prologic I’d be fine with that, too. 😅
@bender Haha ! 😝 I mean we'll squish any bugs that are reasy enough to fix right? 😅
@bender Haha ! 😝 I mean we'll squish any bugs that are reasy enough to fix right? 😅
Woot! Yup, fixed! Baby steps, squashing one bug at a time.
I _thuink_ that's sorted out then. Pulled in the latest deps, repro'd locally, bug gone. So twtxt.net will roll out shortly with the new version in a few mins 👌
I _thuink_ that's sorted out then. Pulled in the latest deps, repro'd locally, bug gone. So twtxt.net will roll out shortly with the new version in a few mins 👌
@bender Yes, I'll see if I can pull in the updated dep now...
@bender Yes, I'll see if I can pull in the updated dep now...
@prologic a new Yarn build is needed to fix it here, right?