you’re running a drm-compilant browser
They also don't want users to be able to use adblockers, that isn't all they're checking for. So this absolutely is the case. Their entire proposal is contradictory.
Nobody is actively working on it now; the same can't be said for Wayland. Recently, it even hit a development low of all time. The only ones working on it are the ones getting paid to work on it, and even then, only those familiar with the codebase. Looking at the history, the only major changes are for Xwayland, and aren't at all often.
If (almost) all of the developers have abandoned something in favor of a newer piece of software that does the job better, I think it's sufficient to say that it's deprecated and unmaintained.
No, I'm thinking of Xorg. The development on it has slowed to less than a crawl, and not because it's feature-complete. It's unmaintainable, and hell to manage for anyone that's not a senior Xorg developer.
The point of this is so that the user can't modify the site at all, despite what the proposal might say. Their goals and non-goals are contradictory.
Running this content in a container will not protect you. Just don't even try to adapt to it. Reject it completely.
Ironic how he chose an X in a strikingly similar style to the (old, unmaintained, and deprecated) Xorg. That was certainly a choice of all time.
That way should not be intrusive ads, and it shouldn't be tracking without user consent.
On their own, exposed to the user in an easily understandable way and easily customizable, they're not bad. They can even help; used right, you can get advertisements relevant to you and your interests, and developers can know what to improve on.
The problem is when this is abused to hell and back by companies that want to strip you of every penny they possibly can, without giving you the choice.
Note what I mentioned in the blog post: most will probably be fine with advertisements so long as they aren't annoying.
You don't get to act the victim when you actively hurt the UX by having avertisements that get all up in your face and want to eek out every single penny like we're slaves.
Coming from someone with an unstable source of income, and that can just barely get by: I'll take advertisements over a subscription/donation based model. Just don't flood your website with them. Or use shitty ad services. And don't make it an unusable experience cough britannica cough
I NEEED ITTTT
the bee logo is so cute and having something to put on my laptop would be amazing :)
The whole idea of expressions is very nice, and I can't imagine using ternary expressions anywhere after learning Rust.
Also implicit returns ❤️
If not friend then why friend shaped?
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:
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.