Firefox just pushed this in Firefox 88 and you do have to go into about:config search for the http3 options and enable it... but it's there.
So I've turned on HTTP3 for LFGSS.
What does this mean for you?
Erm... it's faster?
HTTP3 is basically UDP rather than TCP and the history goes like this:
HTTP 1 = TCP, want to make multiple concurrent requests? OK let's open multiple connections to the server.
HTTP 2 = TCP, want to make multiple concurrent requests? OK, let's open 1 connection to the server and then multiplex within the single connection, oh... those large files are holding up those small files, can't help there.
HTTP 3 = UDP, want to make multiple concurrent requests? OK, let's open a non-blocking UDP connection to the server, multiplex within that, and because it's a spray and pray then no files are being held up.
Something like that (read the RFCs if you care enough).
What does it mean for the site?
If you frequently go into threads with lots of attachments... those threads will be noticeably faster.
What are the risks?
Erm... it's hard to stop a layer 3 DDoS attack based on UDP packets due to how HTTP3 is also encrypted for everything and the encryption means DDoS providers struggle to differentiate between good and bad traffic. Not so bad for this site as the connection identifier encoded in the packets are known, but bad for transit providers where everything is meaningless. But I don't care about that :D
tl:dr If you use latest Chrome or Firefox (with HTTP3 enabled) then big threads with lots of images will load faster.
Firefox just pushed this in Firefox 88 and you do have to go into
about:config
search for thehttp3
options and enable it... but it's there.So I've turned on HTTP3 for LFGSS.
What does this mean for you?
Erm... it's faster?
HTTP3 is basically UDP rather than TCP and the history goes like this:
Something like that (read the RFCs if you care enough).
What does it mean for the site?
If you frequently go into threads with lots of attachments... those threads will be noticeably faster.
What are the risks?
Erm... it's hard to stop a layer 3 DDoS attack based on UDP packets due to how HTTP3 is also encrypted for everything and the encryption means DDoS providers struggle to differentiate between good and bad traffic. Not so bad for this site as the connection identifier encoded in the packets are known, but bad for transit providers where everything is meaningless. But I don't care about that :D
tl:dr If you use latest Chrome or Firefox (with HTTP3 enabled) then big threads with lots of images will load faster.