They didn't.

Sonder did.

You clearly have zero clues whats going on here.

Actually its nothing like that at all.

Its more like paying for food at a restaurant using your Visa card and then complaining to Visa when it tastes bad.

I dont know if you are being a tool on purpose or not.

In case you aren't, let me spell this out as clear as crystal:

- These aren't Marriott properties
- These aren't Marriott bookings
- Marriott has zero control over this whatsoever.

Just because you booked your Sonder stay in the Marriott app, doesnt mean Marriott is responsible for the booking.

Does it suck that Marriott entered into this agreement with this scummy company? Absolutely. But expecting them to somehow wave a magic wand and extend your stay *at a property they don't own and have zero relationship with* is nonsensical.

Needs to be 67 MB for Gen A to care.

No, a service like that would require you to submit your name, and thus the site, as well as the government , would know you accessed that site at that time. Exactly what people dont want. Zero knowledge proofs prevent this because your identity doesnt have to be shared.

If you kill someone and are found at fault, are you not liable?

The technology to verify age without sharing identity has existed for well over a decade.

It is called zero-knowledge proofing and is already rolled out in countries like Estonia.

It is high time that major western countries join the 21st century on this stuff.

There are no easy wins to these problems.

You can't both simultaneously allow adults to use explicit chatbots, and also block them from children, without requiring some form of identity verification.

The real problem is the lack of adopted robust standards by the government for age verification that don't require you to disclose your identity.

The technology to do kind of this already exists, it is called zero-knowledge proofing. it has existed for a decade and is widely deployed in other countries like Estonia.

Most countries are so incredibly far behind the 8 ball on this stuff and they let government and big tech to keep eating away at their freedoms instead of electing and bringing competent technologists into the government to solve the problem.

No one is saying the company is not liable.

If a human kills a kid, they are usually held liable.

Liability and acceptance by society are not the same. 1.9 million people are killed annually in auto accidents. All of those are killed by other humans. We accept this, every day, as a society. It doesn't at all mean that any individual case does not have liability or consequences, it just means we don't shut down the roadways.

... per year already.

No, it isn't. It is YALDE (Yet Another Linux Desktop Environment)

It has nothing at all to do with Ubuntu the company.

Er... it is a GUI. And totally optional. NordVPN supports OpenVPN protocol (as well as IPSec, SOCKS5, and a bunch of others).

The GUI client is to make things easy and to support NordLynx. If you don't want it then don't use it. Complaining about a non-issue is ridiculous.

Its partially a diversion

He also does this so his insiders can make a killing on trading.

There is increasing pressure on companies to take responsibility for their software products. This includes preasure to move towards memory safe languages. This exercise is about getting C++ of the governments naughty lists, so that people can continue to use C++ without extra regulatory overhead and too much risk to the company.

Rust is just a working example of a language with similar performance to C++, whise approach could be copied. The committee opted to not do that and go for something that does not make the language memory safe at all, but that catches enough bugs to be close enough (they hope).

We'll see whether that is implementable, practical and enough to satisfy regulators.

I have hunted my fair share of core dumps in Qt code. Each one is a memory safety fail... it is, just like the rest of C++ not memory safe.

I find it funny that so many C++ devs seem to think using smart pointers means you are memory safe. It does not, there is so much more needed... check what the "safe C++" proposal set out to change, that's what you need tomdo to make C++ memory safe using the approach rust took. It includes fun stuff like new reference semantics, destructive moves and a new standard library.