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.)
woke up a bit groggy, but definitely excited to go run. the temps were b/w 70F-73F with a dew point to match which is fabulous. such a great run and kept a conservative pace for it leaving me feeling strong at the end. wanted to keep going but i know i should ease back in to the longer distances
#running
woke up a bit groggy, but definitely excited to go run. the temps were b/w 70F-73F with a dew point to match which is fabulous. such a great run and kept a conservative pace for it leaving me feeling strong at the end. wanted to keep going but i know i should ease back in to the longer distances
#running
woke up a bit groggy, but definitely excited to go run. the temps were b/w 70F-73F with a dew point to match which is fabulous. such a great run and kept a conservative pace for it leaving me feeling strong at the end. wanted to keep going but i know i should ease back in to the longer distances
#running
woke up a bit groggy, but definitely excited to go run. the temps were b/w 70F-73F with a dew point to match which is fabulous. such a great run and kept a conservative pace for it leaving me feeling strong at the end. wanted to keep going but i know i should ease back in to the longer distances
#running
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.
Meme com duas crianças a rir, uma a deitar leite pelo nariz. Texto diz "yo Mama's so fat she can't save files bigger than 4gb" Spoiler da piada: o filesystem FAT32 não permite ficheiros com tamanho maior que esse, uma frustração habitual
Meme com duas crianças a rir, uma a deitar leite pelo nariz. Texto diz "yo Mama's so fat she can't save files bigger than 4gb" Spoiler da piada: o filesystem FAT32 não permite ficheiros com tamanho maior que esse, uma frustração habitual
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
The recording didn’t turn out so well, because … traffic is still louder. And what’s up with that obnoxious beeping? Meh.
https://movq.de/v/84f2866ded/noise.ogg
The recording didn’t turn out so well, because … traffic is still louder. And what’s up with that obnoxious beeping? Meh.
https://movq.de/v/84f2866ded/noise.ogg
The recording didn’t turn out so well, because … traffic is still louder. And what’s up with that obnoxious beeping? Meh.
https://movq.de/v/84f2866ded/noise.ogg
> I could get rid of the Python part if I just had more LaTeX skills.
You mean doing all this math as macros? That sounds pretty scary. 😱
> I could get rid of the Python part if I just had more LaTeX skills.
You mean doing all this math as macros? That sounds pretty scary. 😱
> I could get rid of the Python part if I just had more LaTeX skills.
You mean doing all this math as macros? That sounds pretty scary. 😱
> I don't believe it's a good idea to wipe it.
Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste.
By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)
> I don't believe it's a good idea to wipe it.
Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste.
By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)
> I don't believe it's a good idea to wipe it.
Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste.
By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)
XDG_STATE_HOME just like I do with XDG_CACHE_HOME. So far, only wireplumber appears in this directory … Hm …
XDG_STATE_HOME just like I do with XDG_CACHE_HOME. So far, only wireplumber appears in this directory … Hm …
XDG_STATE_HOME just like I do with XDG_CACHE_HOME. So far, only wireplumber appears in this directory … Hm …
I’ll keep an eye on labwc, because it’s very promising, and try again in a few years. If I had the resources to get involved with development, I would, but I don’t, sadly.
Hasta a mí me dan lástima los perros con abrigo ⛈️ ⌘ Read more****
docker run \
--net=host \
-e TZ=Europe/Prague \
-v /your-data-dir/data:/data \
--name "mailserver" \
-h "mail.example.com" \
-t analogic/poste.io
docker run \
--net=host \
-e TZ=Europe/Prague \
-v /your-data-dir/data:/data \
--name "mailserver" \
-h "mail.example.com" \
-t analogic/poste.io
docker run \\
--net=host \\
-e TZ=Europe/Prague \\
-v /your-data-dir/data:/data \\
--name "mailserver" \\
-h "mail.example.com" \\
-t analogic/poste.io
docker run \
--net=host \
-e TZ=Europe/Prague \
-v /your-data-dir/data:/data \
--name "mailserver" \
-h "mail.example.com" \
-t analogic/poste.io
That is until the Certificate Authorities get hacked, which I know it "quite hard", as it would take an inside job 🤣 Or state control 🤔