Cloudflare outage on February 20, 2026 • Hacker News Board

Re: Cloudflare outage on February 20, 2026

#131

Post by tovej » Mon, Feb 23, 2026, 1:34 AM UTC

hypeatei wrote: post #128

tovej wrote: post #126

Earlier quoted context omitted.

It may be illegal, but it's not unethical. Doing unethical things because someone pays you would still be unethical. Opposing those while someone pays you is still ethical.

Again, no one is forcing him to be there. He's breaking something on purpose . I think you should read up on ethics because this take "I don't like it therefore whatever I do is ethical" is juvenile.

That's quite the strawman. The reason it's ethical is not that LLM's are unpopular or someone dislikes them. It's ethical because LLMs introduce safety hazards, i.e. they cause harm.

Re: Cloudflare outage on February 20, 2026

#132

Post by lenkite » Mon, Feb 23, 2026, 6:57 AM UTC

PunchyHamster wrote: post #110

blibble wrote: post #12

is this blog post LLM generated? the explanation makes no sense: > Because the client is passing pending_delete with no value, the result of Query().Get(“pending_delete”) here will be an empty string (“”), so the API server interprets this as a request for all BYOIP prefixes instead of just those prefixes that were supposed to be removed. The system interpreted this as all returned prefixes being queued for deletion.…

better explanation here https://news.ycombinator.com/item?id=47106852 but in short they are changing whether string is empty, and query string "pending_delete" is same as "pending_delete=" and will return empty Or, if they specified `/v1/prefixes?pending_delete=potato` it would return "correct" list of objects to delete Or in other words "Go have types safety, fuck it, let's use strings like in '90s PHP apps instead"

If Go supported Optional's, this bug would not have surfaced.

Re: Cloudflare outage on February 20, 2026

#133

Post by pigpag » Mon, Feb 23, 2026, 7:50 PM UTC

alemanek wrote: post #85

kgeist wrote: post #78

It's something we debated in our team: if there's an API that returns data based on filters, what's the better behavior if no filters are provided - return everything or return nothing? The consensus was that returning everything is rarely what's desired, for two reasons: first, if the system grows, allowing API users to return everything at once can be a problem both for our server (lots of data in RAM when fetching…

Returning an empty result in that case may cause a more subtle failure. I would think returning an error would be a bit better as it would clearly communicate that the caller called the API endpoint incorrectly. If it’s HTTP a 400 Bad Request status code would seem appropriate.

[dead]

Re: Cloudflare outage on February 20, 2026

#134

Post by PunchyHamster » Tue, Feb 24, 2026, 1:41 PM UTC

lenkite wrote: post #132

PunchyHamster wrote: post #110

Earlier quoted context omitted.

better explanation here https://news.ycombinator.com/item?id=47106852 but in short they are changing whether string is empty, and query string "pending_delete" is same as "pending_delete=" and will return empty Or, if they specified `/v1/prefixes?pending_delete=potato` it would return "correct" list of objects to delete Or in other words "Go have types safety, fuck it, let's use strings like in '90s PHP apps instead"

If Go supported Optional's, this bug would not have surfaced.

You can probably make it with generics.

But if I was given option to steal one feature out of other languages it would be enums and resulting Result/Optional from Rust

Re: Cloudflare outage on February 20, 2026

#135

Post by asuffield » Thu, Feb 26, 2026, 4:02 PM UTC

blibble wrote: post #12

is this blog post LLM generated? the explanation makes no sense: > Because the client is passing pending_delete with no value, the result of Query().Get(“pending_delete”) here will be an empty string (“”), so the API server interprets this as a request for all BYOIP prefixes instead of just those prefixes that were supposed to be removed. The system interpreted this as all returned prefixes being queued for deletion.…

Hi! I wrote this paragraph. I promise that I'm not an LLM, but I was in about hour 10 of my work day and I was asleep not long after writing this. Any failures in comprehensibility are from exhaustion.

(Other comments have explained the bug so I won't repeat them)