# 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 196320
# self = https://watcher.sour.is?offset=165499
# next = https://watcher.sour.is?offset=165599
# prev = https://watcher.sour.is?offset=165399
How have I missed Linux’s landlock? 🤔 Maybe we’ll get something like OpenBSD’s pledge/unveil some day. For now, landlock appears to be more complicated, but we’ll see how it goes. Gotta play with this some time. 🤔
How have I missed Linux’s landlock? 🤔 Maybe we’ll get something like OpenBSD’s pledge/unveil some day. For now, landlock appears to be more complicated, but we’ll see how it goes. Gotta play with this some time. 🤔
How have I missed Linux’s landlock? 🤔 Maybe we’ll get something like OpenBSD’s pledge/unveil some day. For now, landlock appears to be more complicated, but we’ll see how it goes. Gotta play with this some time. 🤔
[47°09′35″S, 126°43′14″W] Raw reading: 0x66810271, offset +/-2
What a night. The first storm cluster passed us in about 25km distance.

The second one hit us right in the face. The sky was constantly flashing and there was a continuous rumble, not individual thunder. (You can’t really hear it in the video, I was too close to the window …)

https://movq.de/v/e949ae6403/MVI_7687.MOV.mp4

Most of the lightning was inside the clouds, apparently.

https://movq.de/v/e949ae6403/IMG_7648.JPG

No water damage this time, luckily.
What a night. The first storm cluster passed us in about 25km distance.

The second one hit us right in the face. The sky was constantly flashing and there was a continuous rumble, not individual thunder. (You can’t really hear it in the video, I was too close to the window …)

https://movq.de/v/e949ae6403/MVI_7687.MOV.mp4

Most of the lightning was inside the clouds, apparently.

https://movq.de/v/e949ae6403/IMG_7648.JPG

No water damage this time, luckily.
What a night. The first storm cluster passed us in about 25km distance.

The second one hit us right in the face. The sky was constantly flashing and there was a continuous rumble, not individual thunder. (You can’t really hear it in the video, I was too close to the window …)

https://movq.de/v/e949ae6403/MVI_7687.MOV.mp4

Most of the lightning was inside the clouds, apparently.

https://movq.de/v/e949ae6403/IMG_7648.JPG

No water damage this time, luckily.
What a night. The first storm cluster passed us in about 25km distance.

The second one hit us right in the face. The sky was constantly flashing and there was a continuous rumble, not individual thunder. (You can’t really hear it in the video, I was too close to the window …)

https://movq.de/v/e949ae6403/MVI_7687.MOV.mp4

Most of the lightning was inside the clouds, apparently.

https://movq.de/v/e949ae6403/IMG_7648.JPG

No water damage this time, luckily.
[47°09′18″S, 126°43′19″W] Dosimeter fixed
@darren Thanks! 🙏
@darren Thanks! 🙏
@mckinley Thank you! 🙏
@mckinley Thank you! 🙏
This store looks great: https://storyfair.net/helpstoryfairgrow/
🧮 USERS:1 FEEDS:2 TWTS:1016 ARCHIVED:75590 CACHE:2342 FOLLOWERS:17 FOLLOWING:14
Ciberlândia, que música é esta? Texto cinzento em fundo branco: I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know
Ciberlândia, que música é esta? Texto cinzento em fundo branco: I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know, I know
@movq I hear you. We had a full day outside with the scouts. A scouting game in the morning to early afternoon. Luckily, I had a station in the forest. Then cake in the afternoon, barbecue and salad in the evening. But 33°C were just totally terrible. The sweat was running down in streams. I turned seven liters of water and apple juice into sweat in no time.

It's itching everywhere, mozzies ate me alive.
@movq Phew! Quite the opposite from ideal, but could be worse. Finger's crossed that this doesn't repeat.
[47°09′19″S, 126°43′31″W] Dosimeter overflow
As I was writing my latest post on conscious consumption (https://www.davebucklin.com/play/2024/06/27/consumption.html), I learned of Dr. Bronner's 5-to-1 cap on executive compensation (https://www.drbronner.com/pages/about).
As I was writing my latest post on conscious consumption (https://www.davebucklin.com/play/2024/06/27/consumption.html), I learned of Dr. Bronner's 5-to-1 cap on executive compensation (https://www.drbronner.com/pages/about).
As I was writing my latest post on conscious consumption (https://www.davebucklin.com/play/2024/06/27/consumption.html), I learned of Dr. Bronner's 5-to-1 cap on executive compensation (https://www.drbronner.com/pages/about).
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
That heat is driving me crazy. Do I have a fever? Is everything ok? Feels like my head is on fire. 🥵
That heat is driving me crazy. Do I have a fever? Is everything ok? Feels like my head is on fire. 🥵
That heat is driving me crazy. Do I have a fever? Is everything ok? Feels like my head is on fire. 🥵
That heat is driving me crazy. Do I have a fever? Is everything ok? Feels like my head is on fire. 🥵
@prologic It’s a slippery slope, to be honest. If you believe *that* kind of shit, you’re going to believe anything. It’s no surprise that flat earthers and, say, esotericism and right wing idiots mix so well. 🫤
@prologic It’s a slippery slope, to be honest. If you believe *that* kind of shit, you’re going to believe anything. It’s no surprise that flat earthers and, say, esotericism and right wing idiots mix so well. 🫤
@prologic It’s a slippery slope, to be honest. If you believe *that* kind of shit, you’re going to believe anything. It’s no surprise that flat earthers and, say, esotericism and right wing idiots mix so well. 🫤
@prologic It’s a slippery slope, to be honest. If you believe *that* kind of shit, you’re going to believe anything. It’s no surprise that flat earthers and, say, esotericism and right wing idiots mix so well. 🫤
[47°09′41″S, 126°43′38″W] Dosimeter malfunction
Gato en su funda
/https://baldo.cat/media/photos/photo_18329-06-2024_15-42-45.jpg) #catsoftwtxt
Gato en su funda
#catsoftwtxt
Gato en su funda
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_17929-06-2024_15-40-00.jpg) #catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_17829-06-2024_15-39-26.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
Can anyone recommend and/or vouch for a Chrome/browser extension that lets me write rewrite rules for arbitrary links on a page? e.g: s/(www\.)?youtube.com\/watch?v=([^?]+)/tubeproxy.mills.io/play/\1 for example? 🤔
Can anyone recommend and/or vouch for a Chrome/browser extension that lets me write rewrite rules for arbitrary links on a page? e.g: s/(www\.)?youtube.com\/watch?v=([^?]+)/tubeproxy.mills.io/play/\1 for example? 🤔
Can anyone recommend and/or vouch for a Chrome/browser extension that lets me write rewrite rules for arbitrary links on a page? e.g: s/(www\\.)?youtube.com\\/watch?v=([^?]+)/tubeproxy.mills.io/play/\\1 for example? 🤔
Another day, another web app built 😅 This time tubeproxy, which still needs some tidying up project-wise (_bugger all docs, setup guide, etc_), but so far it works quite nicely. If you're curious, you're welcome to try it out at https://tubeproxy.mills.io -- Although technically this meant for internal use (_as I block Youtube at the network on purpose_).

Additional features I'm thinking about next:

- Add to Plex (_on-demand download, tag and update of the Plex archives_)
- Subscribe (_added to my ytdl-sub that subscribes to Youtube channels and stores nicely in Plex_)
Another day, another web app built 😅 This time tubeproxy, which still needs some tidying up project-wise (_bugger all docs, setup guide, etc_), but so far it works quite nicely. If you're curious, you're welcome to try it out at https://tubeproxy.mills.io -- Although technically this meant for internal use (_as I block Youtube at the network on purpose_).

Additional features I'm thinking about next:

- Add to Plex (_on-demand download, tag and update of the Plex archives_)
- Subscribe (_added to my ytdl-sub that subscribes to Youtube channels and stores nicely in Plex_)
@movq Haha I was just testing y'all 🤣 How nuts is this right? 😅
@movq Haha I was just testing y'all 🤣 How nuts is this right? 😅
@prologic Don’t you make it sound like that’s a legitimate thing to believe … 😂
@prologic Don’t you make it sound like that’s a legitimate thing to believe … 😂
@prologic Don’t you make it sound like that’s a legitimate thing to believe … 😂
@prologic Don’t you make it sound like that’s a legitimate thing to believe … 😂
@unexplained_mysteries Anyone here believe in a flat earth? 🌍 hmm? 🧐
@unexplained_mysteries Anyone here believe in a flat earth? 🌍 hmm? 🧐
On my blog: Free Culture Book Club — Nevada, part 4 https://john.colagioia.net/blog/2024/06/29/nevada-4.html #freeculture #bookclub
[47°09′43″S, 126°43′43″W] Transfer aborted
[47°09′39″S, 126°43′41″W] Transfer 50% complete...
[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.~