“Protecting our community," by destroying it. If you don’t have a community, then it can’t be toxic. Were the comments so bad that this was the only solution?

Hmm, i think I mixed it up with the config. There is an all option in swayimgrc.

deleted by creator

You can make it work mostly that way. Create a UKI (unified kernel image including EFI stub loader, kernel, initial filesystem and kernel parameters), then tell uefi to directly boot it. The four steps still run, but using only a single file.

There is some difference I see in the management layer, with more dynamic resource allocation in a cloud infrastructure compared to traditional data center usage.

I think the --all option is this mode.

At least on xorg the gifs I had worked.

Exactly what I expected from them. The same interests that want chat control are here as well.

This sort of thing is the reason that the kernel has its own cve authority / cna now.

It’s interesting, that it would be hard to make a case that there was a “vulnerability” in the ip package. But it seems like this package’s entire purpose is input validation so it’s kind of weird the dev thinks otherwise.

Yes, input validation, probably for forms. What the Dev disputes is that he cannot see a case where it is used in a security critical way where

1. the input format is unknown and
2. it is essential to know if the IP is public or private.

I don’t know how it compares to nsxiv, but imv supports Wayland.

deleted by creator

I am shocked that Facebook employees even see this as a vulnerability. I always considered metadata the valuable part of WhatsApp.

In that case you still have the third party bridge https://github.com/emersion/hydroxide

If you need arm, then you probably have to install libhoudini https://github.com/casualsnek/waydroid_script