Conversation

Notices

1. fen (shadyfennec@aleph.land)'s status on Thursday, 13-Jan-2022 10:13:21 UTC fen

   PSA: If your firefox browser suddenly starts consuming 100% of a CPU core and doesn't seem to load pages anymore, go to about:config, search for the key "network.http.http3.enabled" and set it to false

   They just pushed the most vile and foul update and it broke everything

   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Thursday, 13-Jan-2022 10:13:13 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Mina
     @meena @ShadyFennec For the complexity?
   • Mina (meena@cathode.church)'s status on Thursday, 13-Jan-2022 10:13:14 UTC Mina

     in reply to

     @ShadyFennec i've been distrustful of HTTP/2 since its inception, and then some more of HTTP/3

   • fen (shadyfennec@aleph.land)'s status on Thursday, 13-Jan-2022 10:13:19 UTC fen

     in reply to

     bugzilla thread: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908

   • fen (shadyfennec@aleph.land)'s status on Thursday, 13-Jan-2022 10:13:20 UTC fen

     in reply to

     really excited to read about the postmortem of this one

   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Thursday, 13-Jan-2022 10:41:06 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Mina
     @meena @ShadyFennec > let's implement TCP over HTTP
     
     That doesn't seem like a fair and factual description.
     
     > a new standard replacing TCP
     
     Arguably they kind of did that.
     
     > or a new protocol replacing / supplementing HTTP that runs on a different Port
     
     HTTP/3 replaces/supplements HTTP/1.1 on a different protocol_number/port pair.
     
     > fuck up a perfectly adequate* protocol instead
     
     I've seen more people than you say this. Clearly it introduces new complexity and mistakes to be made, as it introduces more slightly different ways for data to reach the browser.
   • Mina (meena@cathode.church)'s status on Thursday, 13-Jan-2022 10:41:07 UTC Mina

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅

     @clacke @ShadyFennec let's implement TCP over HTTP

     you know who's best at doing this?
     giant companies who are the only ones dictating the new standards, and the only ones actually remotely benefiting from it, due to their sheer scale

     also the only ones who could push thru a new standard replacing TCP, or a new protocol replacing / supplementing HTTP that runs on a different Port, but, nope, they chose their power to fuck up a perfectly adequate* protocol instead.

     ____
     *lest i be misinterpreted: HTTP is not good, not great, it's just that: adequate