Live data from Hacker News

HTTP/3 is everywhere but nowhere

httptoolkit.com

171–180 of 504 posts

Re: HTTP/3 is everywhere but nowhere

#171
post #60

Earlier quoted context omitted.

The normalization of CAPTCHAs for simply reading what ought to be public information strikes me as very alarming, as does characterizing essential privacy and anti-censorship measures like VPNs as "abusive". Something like 1% of HTTP hits pose some risk of spam or fraud, those where somebody is trying to post a message or a transaction or something. The other 99% are just requesting a static HTML document or JPEG (or…

Of course it's alarming. But what's the alternative? > Something like 1% of HTTP hits pose some risk of spam or fraud It doesn't matter if it's a tiny percentage of requests that are spam/fraud. The only thing that matters is the absolute amount, and that's massive. > Static file serving is very difficult to DDoS No it's not, and most pages aren't particularly static. They're hitting all sorts of databases and caches…

Can you explain more specifically the threats faced by your website? Please help us understand what attacks you are currently facing. Are you currently getting DDoSed? Did the DDoSer stop DDoSing when you blocked HTTP 1.1? Did your credit card chargebacks drop by 50%?

---

According to other commenters the main use case for HTTP/3 is ads serving. Should I assume your project is an ad server? I could disable HTTP/3 in my browser to block ads. You see that this is a bit silly, right?

Re: HTTP/3 is everywhere but nowhere

#172

Earlier quoted context omitted.

> side note: sad that .NET and C# are not considered "major I've said it before on here, but the tech community severely underrates .NET today. It's not Windows only (and hasn't been for ~8 years) plus C# is a very nice language. F# is also an option for people who like functional languages. I'd highly recommend giving it a try if you haven't already.

Why would I use C# over any other language though?

It's very productive and kinda nice.

Especially for big backend APIs: https://typescript-is-like-csharp.chrlschn.dev/

Re: HTTP/3 is everywhere but nowhere

#173
> At the same time, neither QUIC nor HTTP/3 are included in the standard libraries of any major languages including Node.js, Go, Rust, Python or Ruby. Curl recently gained supportopens in a new tab but it's experimental and disabled in most distributions.

That doesn't matter too much, since a certain "security" company is doing deep packet inspection and blocking anything that isn't Firefox, Chrome, or Safari.

Re: HTTP/3 is everywhere but nowhere

#174
post #137

Earlier quoted context omitted.

How do you cross compile from linux to macos?

dotnet publish -r osx-x64 --self-contained https://learn.microsoft.com/en-us/dotnet/core/deploying/#pub...

Just like for windows or Linux, in other words. The dotnet tooling is amazingly friction and ceremony free these days.

Re: HTTP/3 is everywhere but nowhere

#175

> At the same time, neither QUIC nor HTTP/3 are included in the standard libraries of any major languages including Node.js, Go, Rust, Python or Ruby. Curl recently gained supportopens in a new tab but it's experimental and disabled in most distributions. That doesn't matter too much, since a certain "security" company is doing deep packet inspection and blocking anything that isn't Firefox, Chrome, or Safari.

It's not even doing that right. I regularly see the same page blocked in Firefox while not being blocked in Chrome, on the same IP and device.

Basically if your browser provides even a tiny bit of privacy, Cloudflare blocks it randomly.

Re: HTTP/3 is everywhere but nowhere

#176

Earlier quoted context omitted.

.NET suffers from the long lasting reputational taint of Microsoft. It was seen as the sworn enemy of open source and Linux, and for good reason. Today’s MS is not what it was back then. But long memories are not a bad thing, really. If .NET suffers a bit from some unfair perception, perhaps that can remind MS and others what happens when you take an aggressively adversarial approach.

The ironic thing? GitHub, VS Code, and TypeScript are all Microsoft products.

GitHub was purchased, which is a bit different.

TypeScript though I had no idea about! Good for them!

Re: HTTP/3 is everywhere but nowhere

#177

Earlier quoted context omitted.

They also severely underrate it's actual usage. For a non "major" language, there sure are a lot of jobs out there. .NET ain't hip.

.NET ain’t hip because many of the shops that use it are dinosaurs in processes and culture.

And many are not. How many Python shops are living in the past? It’s the same problem everywhere.

Re: HTTP/3 is everywhere but nowhere

#178
post #131

Earlier quoted context omitted.

Isn't 5G supposed to solve the mobile latency issue?

The connection to your local tower can have a negligible latency. The connection all the way to the datacenter may take longer. Then, there is congestion sometimes, e.g. around large gatherings of people; it manifests as latency, too.

But from the tower onward it shouldn't be any different from fixed internet connections, except for the gatherings, I'll grant that one.

So then (modern) mobile shouldn't be all that special.

Re: HTTP/3 is everywhere but nowhere

#179

There's some cool stuff & capabilities here. Its surprising to me that uptake has been so slow. Node.js just posted an update on the state of QUIC, which underlies http3 & has had some work over the years. They're struggling with openssl being slow to get adequate API support going. There's efforts that have working books for quic, but the prospect of switching is somewhat onerous. Really unfortunate; so much of this…

I'd love to see that OpenSSL fork drama on the main page of HN. Do you know where this was discussed?

Re: HTTP/3 is everywhere but nowhere

#180

> At the same time, neither QUIC nor HTTP/3 are included in the standard libraries of any major languages including Node.js, Go, Rust, Python or Ruby. .NET actually looking like it has decent support for any teams that are interested[0] (side note: sad that .NET and C# are not considered "major"...). There is an open source C library that they've published that seems rather far along[1] Support for Windows, Linux[2],…

> side note: sad that .NET and C# are not considered "major I've said it before on here, but the tech community severely underrates .NET today. It's not Windows only (and hasn't been for ~8 years) plus C# is a very nice language. F# is also an option for people who like functional languages. I'd highly recommend giving it a try if you haven't already.

I’ve been a .Net developer since it launched, but recently I find myself using it less and less. I’m so much more productive with LLM assistance and they aren’t very good at C#. (Seriously, I thought AI coding was all exaggeration until I switched to Python and realized what the hype was all about, these language models are just so much more optimized for python)

Plus now Microsoft is being a bully when it comes to Cursor and the other VS Code forks, and won’t let the .net extensions work. I jumped through a lot of hoops but they keep finding ways to break it. I don’t want an adversarial relationship with my development stack.

I miss C# and I really don’t like Python as a language, but I don’t see myself doing a lot more C# in the future if these trends continue.

Post reply on HN