Tor doesn't support UDP so no HTTP/3 but one would expect most services would be available for the foreseeable future over HTTP/2 as well.

like websites without javascript?

Working without javascript requires development time. Running old versions of HTTP doesn't. Version 1.1 is going to be fully supported for a long time.

Working without javascript requires money. Running old versions of HTTP requires ????.

Running old versions of HTTP requires nothing because people will need to support legacy devices for a long time, and it's obviously already implemented in all major components (Servers, CDNs, Clients, etc.)

You (will) run HTTP/3, because it is more efficient, meaning that your servers will be able to service more request.

You run HTTP/2 and HTTP/1, because a lot of people are still using that, and you don't want to lose them. This especially applies to mobile devices, many of which are stuck with software that cannot be updated for various reasons.

There's no threat of the majority of websites going HTTP/3 anytime soon. By the time that might be a possibility, Tor will catch up.

"Will" - are you from the future?

If it becomes the dominant way of serving web pages, you should realize that tor will add support.

How can I realise something that may or may not happen?

Everything that goes over UDP is not supported as of 2018 and some volunteer project is going to figure this out?

Hubris.

Unless they lose 99% of their users, there's enough demand. Your level of pessimism on this specific detail is ridiculous. Tor might not last forever, but it won't be lack of HTTP support that kills it.

If you wait a few years for HTTP/3 to settle, proxies will be available that could be glued into tor inside a weekend hackathon.

> If you wait a few years for HTTP/3 to settle, proxies will be available that could be glued into tor inside a weekend hackathon.

In 16 years they have not managed to support UDP and now you say of a project (you are not familiar with...), that they can get it up over a weekend hackathon.

And you are calling me ridiculous?

This speaks volumes for your predictive ability.

Good day, sir!

Do you have a contact address? I could mark my calendar for 2025. "some proxy with HTTP >= 3 and HTTP < 3 will exist" is a very basic prediction. It wouldn't have to be integrated into the tor codebase either, just spawned by the tor process.

Tor doesn't have UDP support right now because it doesn't need it for anything. The last 16 years are not equal to the next 16 years, surprisingly enough.

The first one requires money be spent on every site.

The second one requires that the feature be maintained in major web servers. Which it will be. On a per-site basis, the developer needs to do nothing.

Still not getting it. Every site is hosted. The hosting company needs to spend money on HTTP/2, and be allowed to use it. The networks need to allow TCP through. All the steps down to the transport layer now require legacy maintenance.

Lots of things need to happen for HTTP/2 to 'stay alive'.

Your use of the future tense does not convince me.

The hosting company needs to spend basically nothing, because it's built into the software.

It's built into the software because enough sites will still be using it fifty years from now, even if it's a minority of traffic.

I seriously doubt you'll ever see TCP blocked.

Is there anything that prevents Tor from supporting this protocol?