I've been using OBS on wayland, they got captures working really well a few years ago.
But for VR stuff I've been going back to X11, and I was just last night trying to finish a screen capture program on wayland (w/ kde plasma) and idk I just have to do repeated screenshots ana analyze those > horrible fps, but at least I think I got that working finally after many attempts last year.
Gaming is not really an issue now with DEs that help ppl disable compositions and wine/proton.
I have been having great luck with waypipe (gitlab) as an X11 forwarding alternative (OS X to Ubuntu 24.04). The setup was relatively painless and it 'just worked.' while this might not suit your needs for other reasons I was pleasantly surprised.
I chose my monitor very specifically for low latency, good color reproduction and "high" (as in the screen is higher than 16:9) aspect ratio - in about 2012! and I'm still quite happy with it. 4K is incoming, but only if it's better in all criteria, which became available fairly recently.
A lot of people still seem to buy their monitors without considering latency, which majorly sucks. It feels like the years between power supply efficiency making a difference and the introduction of 80+ efficiency standards.
"To investigate, I used a small Teensy microcontroller to measure click-to-photon latency. It acts as a USB HID mouse and is paired with a light sensor pressed against the screen. I flashed it with an existing Open Source LDAT sketch, with slight modifications. The resulting setup can log hundreds of samples to a CSV file, unattended."
Figured it out, had a random block of Firefox versions less than 147 in my ApplicationController for some reason. Of course my home internet went down though so I’ll push in a few.
If I set my UA to "FUCKIT" I can use the site perfectly fine. Why is there a User Agent Filter that disables the whole website? This should be maybe a warning, not a complete block.
you know, I had setup some analytics filtering based on geoip because I was getting crazy spam traffic from Chine and Singapore, but that should only be affecting analytics not the whole site. Mind if I ask where you're located? (you can email me privately if preferred: me@dchuk.com)
Wasn't there a (proposed) "standard" in 90s (eMediaMark, I remembered) that just added a Header to HTTP in order to have ancient browsers automatically filter adult content.
That would easily be enforceable by making a "kid mode" enabled and locked down by a parent with a password mandatory on devices. Then you could have something like this:
You might have an older GPU that doesn't work with wayland like me. My Radeon HD5870 also won't do Vulkan and anything wayland has never worked properly for me.
I'm not questioning what you are saying, but Wayland's only requirement is DRM, which is a Linux kernel capability that is supported for basically everything that you can push some sort of display cable into. It's for buffer management, and X was also ported to use this API.
Unless you have proprietary X server blobs, you have mostly the same low level route in either case to display stuff, so it's on the exact compositor you have tried, not on the wayland protocol.
reply