(Years ago, in very cold winters, I used to jokingly remark: “Why, oh why did our ancestors move this far up north? Couldn’t we have just stayed in Africa?” Now I’m beginning to understand. 😂)
(Years ago, in very cold winters, I used to jokingly remark: “Why, oh why did our ancestors move this far up north? Couldn’t we have just stayed in Africa?” Now I’m beginning to understand. 😂)
(Years ago, in very cold winters, I used to jokingly remark: “Why, oh why did our ancestors move this far up north? Couldn’t we have just stayed in Africa?” Now I’m beginning to understand. 😂)
I’m beginning to think that xiate’s days might be numbered. I don’t want to worry about GTK shenanigans anymore.
I’m beginning to think that xiate’s days might be numbered. I don’t want to worry about GTK shenanigans anymore.
I’m beginning to think that xiate’s days might be numbered. I don’t want to worry about GTK shenanigans anymore.
https://movq.de/v/63aae3e744/IMG_6561.JPG
https://movq.de/v/63aae3e744/IMG_6561.JPG
https://movq.de/v/63aae3e744/IMG_6561.JPG
https://wayland.app/protocols/virtual-keyboard-unstable-v1
At least my password manager can do auto-typing now. That has been a major deal-breaker for me.
I still won’t be able to reimplement multipass on Wayland, though. 😞 Meh. It’s an important tool in my workflows and I’d hate to give up on it.
https://wayland.app/protocols/virtual-keyboard-unstable-v1
At least my password manager can do auto-typing now. That has been a major deal-breaker for me.
I still won’t be able to reimplement multipass on Wayland, though. 😞 Meh. It’s an important tool in my workflows and I’d hate to give up on it.
https://wayland.app/protocols/virtual-keyboard-unstable-v1
At least my password manager can do auto-typing now. That has been a major deal-breaker for me.
I still won’t be able to reimplement multipass on Wayland, though. 😞 Meh. It’s an important tool in my workflows and I’d hate to give up on it.
ls all the darn time. 😂 Maybe it’s not even a bad habit. At the shell, you better make sure you’re operating on the correct set of files before issuing rm * (or grep -r, for that matter 😅). But I admit that I do it a bit compulsively, yeah.
ls all the darn time. 😂 Maybe it’s not even a bad habit. At the shell, you better make sure you’re operating on the correct set of files before issuing rm * (or grep -r, for that matter 😅). But I admit that I do it a bit compulsively, yeah.
ls all the darn time. 😂 Maybe it’s not even a bad habit. At the shell, you better make sure you’re operating on the correct set of files before issuing rm * (or grep -r, for that matter 😅). But I admit that I do it a bit compulsively, yeah.
> I feel like I've finally earned my curmudgeonly personality 😆
Wait, that’s how I feel about 40. Don’t tell me I have to wait until 50! 😂
> I feel like I've finally earned my curmudgeonly personality 😆
Wait, that’s how I feel about 40. Don’t tell me I have to wait until 50! 😂
> I feel like I've finally earned my curmudgeonly personality 😆
Wait, that’s how I feel about 40. Don’t tell me I have to wait until 50! 😂
https://movq.de/v/5db90175f9/photo.jpg
https://movq.de/v/5db90175f9/photo.jpg
https://movq.de/v/5db90175f9/photo.jpg
> The guardian of the garage.
😂
> The guardian of the garage.
😂
> The guardian of the garage.
😂
The difference in brightness is much more challenging. I was surprised that I could capture both Jupiter and the Moon in one photo at all. 😲
The difference in brightness is much more challenging. I was surprised that I could capture both Jupiter and the Moon in one photo at all. 😲
The difference in brightness is much more challenging. I was surprised that I could capture both Jupiter and the Moon in one photo at all. 😲
https://movq.de/v/d11768d3d9/wat.jpg
https://movq.de/v/d11768d3d9/wat.jpg
https://movq.de/v/d11768d3d9/wat.jpg
https://movq.de/v/83ef48f947/IMG_6548.JPG
https://movq.de/v/83ef48f947/IMG_6548.JPG
https://movq.de/v/83ef48f947/IMG_6548.JPG
https://movq.de/v/0b0c522e8c
https://movq.de/v/0b0c522e8c
https://movq.de/v/0b0c522e8c
> To elaborate, I don't want to add new commands or config options or some similar such before we know how security as a whole is going to play out, because we'll have to support them forever and it's unlikely that we'd come up with a solution now that doesn't end up being inconsistent with our later work.
Understandable.
I wasn’t quite aware that things are still “in flux” so much. 🤔
> To elaborate, I don't want to add new commands or config options or some similar such before we know how security as a whole is going to play out, because we'll have to support them forever and it's unlikely that we'd come up with a solution now that doesn't end up being inconsistent with our later work.
Understandable.
I wasn’t quite aware that things are still “in flux” so much. 🤔
> To elaborate, I don't want to add new commands or config options or some similar such before we know how security as a whole is going to play out, because we'll have to support them forever and it's unlikely that we'd come up with a solution now that doesn't end up being inconsistent with our later work.
Understandable.
I wasn’t quite aware that things are still “in flux” so much. 🤔
That’s what I would have expected.
(The text in the dialog is a lie, though. I cannot find the corresponding setting to allow/deny making screenshots. 🤷 Whatever.)
That’s what I would have expected.
(The text in the dialog is a lie, though. I cannot find the corresponding setting to allow/deny making screenshots. 🤷 Whatever.)
That’s what I would have expected.
(The text in the dialog is a lie, though. I cannot find the corresponding setting to allow/deny making screenshots. 🤷 Whatever.)
But one valid use case of this X11 “feature” is to make screenshots.
To make screenshots work on Wayland, this protocol exists:
https://wayland.app/protocols/wlr-screencopy-unstable-v1
What I would have expected is that, when I run a screenshot tool (e.g.,
grim), the compositor asks me: “Hey, that program wants to make a screenshot, is that OK?” (That might be a bit annoying, but it’s the only way I can think of to avoid programs silently taking screenshots in the background.)What happens instead is that
grim just makes a screenshot, just like on X11.I searched the bug trackers of some compositors (labwc, sway, hyperland), but couldn’t find any discussions about this.
Aren’t we almost back to square one now … ? The only advantage is that compositors now *could* ask, because there’s a well-defined protocol. But in practice they don’t. Hm.
cc @mckinley since you seem to have some more experience with Wayland.
But one valid use case of this X11 “feature” is to make screenshots.
To make screenshots work on Wayland, this protocol exists:
https://wayland.app/protocols/wlr-screencopy-unstable-v1
What I would have expected is that, when I run a screenshot tool (e.g.,
grim), the compositor asks me: “Hey, that program wants to make a screenshot, is that OK?” (That might be a bit annoying, but it’s the only way I can think of to avoid programs silently taking screenshots in the background.)What happens instead is that
grim just makes a screenshot, just like on X11.I searched the bug trackers of some compositors (labwc, sway, hyperland), but couldn’t find any discussions about this.
Aren’t we almost back to square one now … ? The only advantage is that compositors now *could* ask, because there’s a well-defined protocol. But in practice they don’t. Hm.
cc @mckinley since you seem to have some more experience with Wayland.
But one valid use case of this X11 “feature” is to make screenshots.
To make screenshots work on Wayland, this protocol exists:
https://wayland.app/protocols/wlr-screencopy-unstable-v1
What I would have expected is that, when I run a screenshot tool (e.g.,
grim), the compositor asks me: “Hey, that program wants to make a screenshot, is that OK?” (That might be a bit annoying, but it’s the only way I can think of to avoid programs silently taking screenshots in the background.)What happens instead is that
grim just makes a screenshot, just like on X11.I searched the bug trackers of some compositors (labwc, sway, hyperland), but couldn’t find any discussions about this.
Aren’t we almost back to square one now … ? The only advantage is that compositors now *could* ask, because there’s a well-defined protocol. But in practice they don’t. Hm.
cc @mckinley since you seem to have some more experience with Wayland.
Back in the days with AwesomeWM, I made a special layout that would keep the windows smaller: https://www.uninformativ.de/desktop/2010-09-28--awesome3-termfair-black.jpg
Back in the days with AwesomeWM, I made a special layout that would keep the windows smaller: https://www.uninformativ.de/desktop/2010-09-28--awesome3-termfair-black.jpg
Back in the days with AwesomeWM, I made a special layout that would keep the windows smaller: https://www.uninformativ.de/desktop/2010-09-28--awesome3-termfair-black.jpg