00:05 ids1024: Yeah, not much need for a WaylandX yet, but I'm sure someone will be scrambling to create it once apps and toolkits start requiring Wayland, but they are running a driver or window manager that requires X.
03:48 orowith2os[m]: I need to put aside time to figure things out again, I wanted to make a WaylandX !
03:48 orowith2os[m]: (As I've probably mentioned here, and in other places, countless times) so apps could stop depending on X *and* Wayland but Life Happened™
04:49 t0mmy: test
04:49 t0mmy: hello!
04:50 t0mmy: I need some Sway help, but the Sway IRC is totally dead
05:15 fluix: hey, what's up? also, the sway IRC isn't dead
05:26 kchibisov: t0mmy: sway is on libera.chat.
05:35 t0mmy: oh damn sorry I stepped away
05:35 t0mmy: Yeah I know it's on Libera but i never see any action
05:35 t0mmy: I'm trying to set my displays with sway output and nothing seems to have any effect
05:37 t0mmy: How do I explain this
05:38 t0mmy: My left display is my laptop, and it's 1600x900 and my right display is a 27 inch 1440p monitor
05:38 kchibisov: I'd suggest to continue in sway channel.
05:38 t0mmy: Alright
10:57 vincejv: Hoping this list will grow smaller this 2024: https://community.kde.org/Plasma/Wayland_Known_Significant_Issues
14:09 dubiousness: It's been shrinking
18:39 Typer: Is there a way for a Wayland client to move its window around?
18:40 immibis: a design tenet of wayland is that clients aren't allowed to know where their windows are
18:42 immibis: there have been some proposals to let wayland clients control window positioning without really knowing their window positioning. I'm not sure if any have been widely adopted in the last few months since I read about this.
18:45 Typer: I think I have a vague idea as to why it is a tenet & not allowed. But just to be sure, is it for privacy/security?
18:47 Typer: Also I'm asking because I was curious if it would be possible to make something akin to: https://www.youtube.com/watch?v=QTMIWD4QooE in Wayland.
18:49 kennylevinsen: Typer: privacy, but also to avoid bad design patterns from X11 that strongly relied on everything being exposed to and controllable by anything
18:52 kennylevinsen: Instead, Wayland reveals nothing and gives control of nothing by default, with explicit protocols for doing specific things where needed
18:53 Typer: kennylevinsen: I do agree with the notion that it shouldn't be in the base protocol. However, surely the privacy concern isn't much of a issue as the compositor/server can ask prompt user for permission for such functionality?
18:54 kennylevinsen: And no, you do not know where your window is positioned, the existence or position of any other windows, nor are you able to move windows.
18:55 Typer: By chance, are there any extension/non-base protocols that do include this functionality?
18:56 kennylevinsen: No
18:56 kennylevinsen: But it would possibly work under Xwayland
18:57 kennylevinsen: Xwayland reveals X windows in its comtrol, but is blind to other Wayland windows of the display server
19:01 kennylevinsen: (As for doing it natively, a protocol could be proposed to allow it - the hard part is consensus, as this is generally not a direction the community has wanted to go in)
19:05 Typer: Sorry, I'm not quite familliar with the in-outs of the wayland protocol development. So I've got no clue what the direction is.