Interesting. Do you know why? I've only ever tried launching nested instances of Sway (the compositor I use) which each use their own sockets and render as a client to the parent compositor and that worked fine. Does it have something to do with rendering to a real display?

I remember this being brought up early in Wayland development. The stance was taken that it wasn't a popular enough use case to be worth putting work into. I don't think there's any real technical reason why it couldn't be done, but I don't know. I'm not familiar with the architecture of Wayland.

I think seatd allows this now? So it works on the rather small sliver of distros that don't run systemd.

> And Wayland doesn't support being able to have multiple logons, each with their own independent desktop, simultaneously like X does.

Not sure what you're referring to. I'm using wayland and I can open multiple desktops via gdm.

I think he means multiple simultaneous seats, and IIRC this is a limitation of systemd-logind, not wayland itself (it works on seatd, though that makes you manage your own XDG_RUNTIME_DIR, so I guess pick your poison).

multiple seats of the same user?

Sure, if you're willing to multiplex your own XDG_RUNTIME_DIR. Hence "pick your poison".