Earlier quoted context omitted.
Same on Android, insane that people aren't validating for mobile in current year
Insane author here. I think I just fixed this issue, if you wanna give it another try!
Works, thanks!
State of multi-player Wayland
101–110 of 115 posts
Re: State of multi-player Wayland
#102I remember the multiplayer of Mahjong on the Amiga worked by just plugging in a second mouse. Voila, two pointers.
I have fond memories of playing Settlers in split screen this way on the Amiga
Re: State of multi-player Wayland
#103The original title, "State of multi-player Wayland" is a much better summary of the article. This ain't just about the pointers! In fact, the author is very explicit about that: > I think there could be a term that’s describing this concept even better – in the title of this post, I picked “multi-player”, to make clear that it’s mostly about multiple people who are collaborating. I’ve also seen “multi-cursor” or “mul…
In fact, you can also have a different touch input devices per seat!
I'm not aware of actual hardware that would make this feasible, but if you invent a touchscreen which recognises between two people's different fingers, you could have a client which tracks who clicks where without any protocol changes.
Re: State of multi-player Wayland
#104> This is obviously not a great solution, and VNC in general feels like ancient technology It's not obvious to me. This looks like software ageism. :) There are at least 2 things that could be done to improve performance in the author's setup: 1. Use the --gpu flag which enables dmabuf capture and h264 encoding via vaapi. 2. Connect using a dedicated VNC client like TigerVNC. This reduces latency by roughly 50 ms. Fo…
Well software has gradually improved and VNC hasn't so of course it's "software ageism". In any case if you were seriously not aware of VNC's shortcomings compared to modern alternatives:
1. Hilarious security. Passwords silently truncated to 8 characters, etc.
2. Inefficient graphics. Very laggy on all but the best connections. Just sending an H.264 video stream is better these days.
3. No seamless window mode.
4. I've never needed it tbh but I doubt it supports remote sharing of USB, printing, audio, GPU etc
Re: State of multi-player Wayland
#105Focus of controls is the hard part. You end up needing a Per-seat version of focus in an application.
Yup, and it's quite non-trivial.
The typical GTK application out there can't handle multi-touch and can rarely even handle several mouse events (e.g.: mouse-wheel scroll while dragging), so I doubt they have full blow support for multiple seats.
Re: State of multi-player Wayland
#106While op uses systemd/udev's internal property mutation mechanism to configure seats, not that sway (and likely other compositors) allow you to just configure the device-to-seat assignment in your configuration or even at runtime.
Re: State of multi-player Wayland
#107Very timely post. I wonder, is it possible to clone one single mouse cursor, to duplicate exactly same actions on two windows placed side by side?
Re: State of multi-player Wayland
#108> This is obviously not a great solution, and VNC in general feels like ancient technology It's not obvious to me. This looks like software ageism. :) There are at least 2 things that could be done to improve performance in the author's setup: 1. Use the --gpu flag which enables dmabuf capture and h264 encoding via vaapi. 2. Connect using a dedicated VNC client like TigerVNC. This reduces latency by roughly 50 ms. Fo…
Well software has gradually improved and VNC hasn't so of course it's "software ageism". In any case if you were seriously not aware of VNC's shortcomings compared to modern alternatives: 1. Hilarious security. Passwords silently truncated to 8 characters, etc. 2. Inefficient graphics. Very laggy on all but the best connections. Just sending an H.264 video stream is better these days. 3. No seamless window mode. 4. I…
As the author of wayvnc, I would say that I'm pretty well aware of what VNC can and cannot do. The RFB protocol (VNC) has improved over time like other protocols.
1. Wrong. There are many extensions that improve upon authentication and encryption.
2. This mostly depends on the implementation, and not necessarily the protocol and/or its extensions.
3. This would require deep integration with the window system on both sides, so I doubt that this is even a thing with RFB on Linux. There certainly aren't any wayland protocols to do this.
4. No one has ever asked me to implement any of that with the exception of audio, but there is also an extension for that.
Re: State of multi-player Wayland
#109Sexy Flanders
Re: State of multi-player Wayland
#110Earlier quoted context omitted.
Well software has gradually improved and VNC hasn't so of course it's "software ageism". In any case if you were seriously not aware of VNC's shortcomings compared to modern alternatives: 1. Hilarious security. Passwords silently truncated to 8 characters, etc. 2. Inefficient graphics. Very laggy on all but the best connections. Just sending an H.264 video stream is better these days. 3. No seamless window mode. 4. I…
As the author of wayvnc, I would say that I'm pretty well aware of what VNC can and cannot do. The RFB protocol (VNC) has improved over time like other protocols. 1. Wrong. There are many extensions that improve upon authentication and encryption. 2. This mostly depends on the implementation, and not necessarily the protocol and/or its extensions. 3. This would require deep integration with the window system on both…
Extensions extensions extensions...
> There certainly aren't any wayland protocols to do [seamless windows]
I think wprs can do this (it calls it "rootless") but I haven't actually got around to trying it yet.