Technology

37551 readers

220 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

374

Elon Musk says Twitter logo to change, birds to be gradually abandoned (www.cnn.com)

submitted 1 year ago by [email protected] to c/[email protected]

175 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

I used to run a multi-monitor desktop setup with Xorg, via the nVidia drivers. Two identical monitors, single framebuffer, no scaling, no tearing, single vsync.

That was quite a while ago, and it worked great. Then I discovered I could run an nVidia and an AMD card, both at the same time, on Windows 7, so made the switch... but still.

"feature" that any application can keylog on Xorg

Isn't that still a "feature" of all PC desktops? https://github.com/Aishou/wayland-keylogger

XKCD 1200

Some good ideas here, but Windows/Linux are still lagging behind: https://news.ycombinator.com/item?id=25971395

[–] [email protected] 2 points 1 year ago

I used to run a multi-monitor desktop setup with Xorg, via the nVidia drivers. Two identical monitors, single framebuffer, no scaling, no tearing, single vsync.

One monitor, one framebuffer, an old use case that for some doesn't even exist now, inefficient and slow tearing prevention, laggy vsync.

That wasn't a multi-monitor desktop setup. That was a hacked together multi-display, single-screen setup.

Also why would you link an LD_PRELOAD attack? That's not Wayland-specific in any way. Any other protocol and library is vulnerable to that too. But let's point out one major issue with that: the LD_PRELOAD needs to be loaded in before the compositor in order to be relevant. With X, you can do that at runtime. Let's also read the README from the repository:

This program is in no way meant as criticism of the Wayland project. It simply demonstrates that creating a secure desktop requires more than just a few server-side restrictions.

Wayland isn't the only software we need for a secure desktop; it just handles making the display secure. For libraries and application sandboxing, you want Flatpak, and we're making progress on dynamic permissions there.

So? What's your point? Nothing here is a Wayland-specific argument. Your setup wasn't functional, it was fundamentally a hack, and one that not-NVIDIA/Intel/AMD hardware doesn't support. Your argument is falling flat on its face.