j0057

In the Apple ecosystem, passkeys are stored in your iCloud, and access to the passkeys is device bound. So if I generate a passkey on a MacBook, I can then use it from my iPhone as well, because it's encrypted to all my hardware devices.

It takes very little money to rent massive botnet capacity to perform crippling DDOS attacks. Unfortunately there are only very few CDNs capable of absorbing that kind of attack.

No, lack of maintainers and maintenance on Xorg would have made Linux desktop unviable altogether. High DPI and fractional scaling are very badly supported on Xorg, and architecturally impossible to build.

Wayland is where development happens, so for better or worse, that is what you'll have to use. If you don't like it, go maintain Xorg, if you can't, you're in no position to complain.

I sense a lot of conservative "they took away our X11 freedom" and I have no understanding for it.

I'm not saying that Kubernetes isn't complex, I'm saying it's a fallacy to claim that the Hashicorp stack in any way manages to be less complex in practice. All of these moving parts are unavoidable if you want to run software at scale, Kubernetes is just way better engineered than the Hashicorp stack, if only for not depending on dockerd.

Docker is not for production. Nomad at scale in practice needs a lot of load-bearing Bash scripts around it: for managing certs, for external DNS, you need Consul for service discovery, Vault for secrets.

At that point, is Nomad still simple? If you're going to take on all of the essential complexity of deploying software at scale, just do it right and use Kubernetes.

Source: running thousands of containers in production.

> A partially typed password would be output to standard input if a timeout occurred when Defaults pwfeedback was not enabled (GHSA-q428-6v73-fc4q).

> Timestamp files did not take into account the setting of the Defaults targetpw and Defaults rootpw (GHSA-c978-wq47-pvvw)

> Also this will completely disable any new phone OS' being developed. Why would anyone bother when you can't verify your wallet to do anything online.

This already the case today, you can't run your bank's app or government eID apps on anything but Google or Apple devices.

In the Netherlands we have 'focus cameras' now that specifically detect smartphone use while driving, with hefty fines of €430. These cameras are mobile as well, so they get placed on different spots over time.

It's not like the browsers can just switch to some better maintained XSLT library. There aren't any. There are about 1.5 closed-source XSLT 3 implementations, Altova and Saxonica. I don't want to sound ageist, but the latter is developed by the XSLT spec's main author, who is nearing retirement age. This library is developed behind closed doors, and from time to time zip files with code get uploaded to GitHub. Make of that what you will in terms of the XSLT community. For all of its elegance, XSLT doesn't seem very relevant if nobody is implementing it. I'm all for the open web, but XSLT should just be left in peace to slide into the good night.

A submarine is a boat and boats sail.