Luke-Jr

In theory, PROT_SAO should be useful for qemu, and trivial to make patches implementing there. That's assuming the kernel actually sets it, though. The problem I encountered when I set out to do it a year or so ago, was that I couldn't find a good test case to fail without it...

Why not just ONE back and forth shipping? And hold debugging until the user reports if the replacement fixed it...

A number of users on IRC also said they would be priced out by any 50% premium increase...

Is it indeed possible to eradicate mosquitoes? Outside my house at certain parts of the day, there's tons and it only takes a few seconds to get swarmed. :(

What is the latest-and-greatest mosquito extermination tech?

Doesn't he know there are parental control apps?

(Although my 10 year old figured out how to bypass those in a matter of days each time I closed the previous bypass-hole... and that was using a rooted OS I could SSH into. So maybe not so effective.)

Alpha blending and retaining the contents of windows doesn't need a full-blown compositor...

1) The UNIX security model puts users all in the same security domain. It's a given that a process running as user X can do whatever it wants with another process running as user X. I agree there may be better security models possible and even desirable in 2019, but at the end of the day, those are new and different security models. Does Wayland target standard UNIX security models, or does it require a specific new security model?

1b) The only really secure sandbox in 2019 appears to be complete hardware isolation. With Xpra, I can do this, and have windows from all my different security domains mapped on the same rootless display. I don't see any way to do the same with Wayland? (In fact, Xpra is buggy enough that if Wayland has a way to do this, it might be a killer feature and convince me to switch!)

2) Even GLES doesn't work without 3D acceleration stuff. I'm currently using a Radeon 7950, but only with the stock fbdev driver due to unresolved kernel bugs using the radeon driver. While my CPU can handle even full OpenGL with 3D games, I don't care to waste it on mere compositing.

It can't actually be used to exploit SPV clients at all, since having even a single destination address puts the transaction over 64 bytes in size.

I guess I'll bid farewell to the Slack communities I've been participating in. I'm not interested in using a browser or installing additional software for chat.

Maybe Google will push Nest to comply with the GPL terms? They're currently missing the (required by GPLv2) build/install stuff from their source code releases... I've been unable to get root on mine so far :(