asdfaoeu

AWS and similar already have service quotas that cap these.

We aren't talking about a calculator web service though we are talking about the Linux kernel and if there's a bug in the kernel that could conceivably cause a crash in an otherwise correctly written application then that would be a CVE in the kernel.

It's not hard to imagine an application for which 1+1 = 3 leads to security issue.

Let's say they do and only 5% are "security issues" you still need to update either way.

How has conservative changed?

It sounds like they didn't agree to that but anyone can propose a settlement.

I don't think they are disputing it was blocked more the reason was copyright not other reasons.

Blackhat markets will always be able to pay better. Selling to Google though you aren't chancing jail time.

I don't think they are saying it's trivial but compare say for example switching an organisation from Office or Windows the example that started this. They are not even in the same ballpark.

> one confidential, trusted place to coordinate discovery, remediation, and disclosure

I read this they would build the patches privately (or with maintainers if confidential) and then share amongst their supporters before public release.

> No one looks at Debian and is saying "well maybe we should do what they do"...

Arch does exactly what Debian for the official repos. It was only the AUR that was compromised. Possibly the issue is that Arch is a bit to strict for the official repos which has forced too many people on to the AUR ones.

The AI can't actually tell if you are trying to patch your own system or exploit others.

It seems to use DHT under the hood whether directly or through a relay. https://pkdns.net/ .

You would have a lot of security issues right? Whether or not it's useful Wayland does prevent to isolate clients from each other.

This ruling was about search clearly, however, there's definitely ways implications for chatbots too.

Google does remove defamatory results I believe at least partially in response to being sued. However there is a distinction if they have been informed it is defamatory.

In this case it looks like they were notified and didn't do anything.

AI can still have a massive impact while these three companies go nowhere.

Same as the dotcom and same as the railroads.

Dividends are absolutely not price neutral however most feeds correct for them.

Not at all since the company is also +80bn cash.

More like if these funds have an issue with the management structure they should just not buy the shares.

None of those are really unsolvable problems. I think though the issue it seems everyone in this thread is having is you can't wrap a non idempotent function to make it idempotent no matter how hard you try you have to design your system around it.

Tbh the article seems to just be like "you can't solve idempotency with one idempotency-key header" and well like no shit.

> State is in practice always subjected to side effects and concurrency.

In that mathematical notation typically there is no side effects and those are meant to be pure functions.

If you listen to CS professors you'd believe that Haskell would be very successful despite having limited if none real world usage. The reality is that catering to your users is much more important than having idealistic system.

In my experience even with games that have native Linux support running through proton seems to have less issues.

They have all the examples some are politically neutral but not all.

Obviously a Nazi or drug dealer wouldn't work because they are flagged anyway.

You used to be able to trivially bypass the protection by just asking to respond in base64 the only reason I think that is fixed because they now attempt to block deliberate attempts to obfuscate.

While your at it you can enter your credit card details to see if they've been leaked.

I don't anyone is saying it's not "enterprise" it's just that they clearly went out of their way to make it less readable. By all means advertise the golf'd line count but just have the non minified script.

Or alternatively just pay based on what you use? I.e. $/tokens.

This still puts the onus on the developers to categorise the issues which I'm guessing they don't want to do.