>>106369707
> messaging, fixed?
None of that is true.
Wayland is all about messaging, which never worked over waylands lifetime, and only half-assed fixed recently…. It’s not there now, never will be, snd rapidly getting worse.

>>106359648
If you look through the code of wayland, it’s pretty clear they are just doing the equivalent of pushing papers around.

Like, to fix the core wayland message passing from going into a busy-wait loop when you give it a 4097 byte message (Secure, eh?) they simply hard-coded the message size making the dynamic message size code essentially dead because they really didn’t know what else to do, and for this one line diff they produced novels of text to make it look like they were doing something.

It’s going to be a whole new attack surface so eveyone with a wayland app thatcan get on your machine can have their own built-in “Recall” like features.

>>105893092
> wayland secure
Don’t send wayland a 4097 byte message though!

>>105871402
Wayland is an extreme security risk.
They just “fixed” this DOS attack that makes it burn CPU forever in an infinite poll loop by hardcoding the buffer size, and now the dynamic buffer resizing code is dead.

In the 90s, on X on sun machines, we were already using 8k packets over loopback (just memory with access controls, really).

The problem is the wayland perpetrators really don’t seem have any experience in software development, computer architecture, networking, graphics, etc, so you’ve got this thing where if you send it a 4097-byte message, it’s now permanently burning a core 100%

>>105824491
> security?
Let’s put it thus way, for the first 10 years of wayland’s life, it was subject to DOSing CPU infinite loops if anything sent it a message bigger than 4096 bytes causing a (random, hard-coded) core protocol change last year.
This is despite the fact it handles dynamic buffer resizing. Well, maybe no longer… code is there though. Dead code.
This is in the fundamental message loop.
They’re literally nowhere.