facebook and porn are still driving tech forward
I would not name facebook close to something good like porn.
Thanks for the input, coomer.
The majority of Facebook's traffic now uses QUIC and HTTP/3
11–20 of 149 posts
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#12Is this down for anyone else?
Have you blocked facebook network wide?
Check this - https://web.archive.org/web/20201021174206/https://engineeri...
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#13By the way, even though it is not yet turned on by default, http3 support is present in Firefox and can be activated by toggling 'network.http.http3.enabled' in about:config to true. I have had it enabled for a few weeks and everything seems okay except that rarely I've noticed a few sites not loading the first time I visit them but needing a 'refresh', but I'm not sure if this is because of the new QUIC code or just…
Where can I put my money on cache coherency?
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#14For Chrome users, this open source extension will tell you what protocol the browser is using for each website being accessed: https://chrome.google.com/webstore/detail/http-indicator/hgc...
Unfortunately permissions to access everything on every website are way to broad for a niche extension like this. There's no guarantee it won't be sold to a malware developer in a month. If you want to use it, I suggest cloning the repo and loading it as an unpacked extension to avoid auto updates.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#15> we refer to QUIC and HTTP/3 together as QUIC My understand is that HTTP/3 always means QUIC is used according to the standard. But that QUIC can be used for other protocols as well. FB's terminology seems to be backwards.
I think they're talking about Google QUIC, which formed the basis for both IETF QUIC and HTTP/3; Facebook has been deploying Google QUIC for a long while now maybe, AFAIK. The people at fault here are probably the IETF lol.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#16> we refer to QUIC and HTTP/3 together as QUIC My understand is that HTTP/3 always means QUIC is used according to the standard. But that QUIC can be used for other protocols as well. FB's terminology seems to be backwards.
It's rather frustrating when people do this; for the rest of the article, when saying QUIC do they mean theur terminology that is actually QUIC and HTTP/3 or do they mean QUIC the TCP alternative? They use both.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#17> we refer to QUIC and HTTP/3 together as QUIC My understand is that HTTP/3 always means QUIC is used according to the standard. But that QUIC can be used for other protocols as well. FB's terminology seems to be backwards.
I think they're talking about Google QUIC, which formed the basis for both IETF QUIC and HTTP/3; Facebook has been deploying Google QUIC for a long while now maybe, AFAIK. The people at fault here are probably the IETF lol.
We never deployed Google QUIC. It was always IETF QUIC. Referring to them together as QUIC was just for expedience, since the main benefits came from the QUIC layer, not the HTTP layer.
HTTP/3 implies IETF QUIC. IETF QUIC itself can be used for non-HTTP protocols, though, just like TCP can be used for protocols that aren't HTTP/2.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#18Is this possible with NodeJS + express already? I didn't see any package for that or config
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#19By the way, even though it is not yet turned on by default, http3 support is present in Firefox and can be activated by toggling 'network.http.http3.enabled' in about:config to true. I have had it enabled for a few weeks and everything seems okay except that rarely I've noticed a few sites not loading the first time I visit them but needing a 'refresh', but I'm not sure if this is because of the new QUIC code or just…
Where can I put my money on cache coherency?
I’ll take that bet and I will give you a generous 1:10 bet odds ratio.
So, if you give me $1000 dollars as your stake then:
- If you are wrong I get to keep the whole $1000
- If you are correct then I will give you $100 of your money back. (Leaving me with $900 of your money still hehe).
In other words what I am saying is, I think you are correct in what you said ;)
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#20Earlier quoted context omitted.
I think they're talking about Google QUIC, which formed the basis for both IETF QUIC and HTTP/3; Facebook has been deploying Google QUIC for a long while now maybe, AFAIK. The people at fault here are probably the IETF lol.
We never deployed Google QUIC. It was always IETF QUIC. Referring to them together as QUIC was just for expedience, since the main benefits came from the QUIC layer, not the HTTP layer. HTTP/3 implies IETF QUIC. IETF QUIC itself can be used for non-HTTP protocols, though, just like TCP can be used for protocols that aren't HTTP/2.
Thank you for the clarification. I'm sure you're looking forward to WebTransport+QUIC as well, I know I am. I'm already doing some little tweaks to our WebSocket RPC and bulk transfer layers to resemble WebTransport so it's an easy drop-in when the QUIC transport becomes available, or when there's a reasonable implementation of WebTransport+HTTP/3 (the other middle ground).
Maybe I can publish the virtual “WebSocketTransport” thing once I'm satisfied with it.