Firefox 90 supports Fetch Metadata Request Headers

Post by The_rationalist » Mon, Jul 12, 2021, 2:48 PM UTC

lallysingh wrote: post #19

contravariant wrote: post #13

Earlier quoted context omitted.

You're gonna have to support the statement that ESNI is fundamentally flawed a bit better for that argument to work.

From Mozilla link above: Since publication of the ESNI draft specification at the IETF, analysis has shown that encrypting only the SNI extension provides incomplete protection. As just one example: during session resumption, the Pre-Shared Key extension could, legally, contain a cleartext copy of exactly the same server name that is encrypted by ESNI. The ESNI approach would require an encrypted variant of every ext…

Post by boba7 » Mon, Jul 12, 2021, 2:52 PM UTC

Post by dbg31415 » Mon, Jul 12, 2021, 2:56 PM UTC

floatingatoll wrote: post #29

dbg31415 wrote: post #20

Any idea when they'll fix Firefox so you can make streaming calls without turning your MBP into a toaster? 40x the battery usage vs. Safari when on a streaming call. It's so painful. Heh, literally. The machine gets too hot to hold comfortably. It's still my primary browser, but optimization is needed. Sucks to have to change browsers just to make calls. We live on streaming calls now. This has been an issue since at…

That sounds like a reproducible bug report, with an easy test case (“run this script and measure laptop battery life, in Firefox and Safari”). If you haven’t already provided that in a bug report to the software developers, you should do so. Shopping your concern to an unrelated thread about security headers isn’t likely to get far on HN, certainly nowhere near as much as a testable bug would.

Post by da_chicken » Mon, Jul 12, 2021, 3:00 PM UTC

dbg31415 wrote: post #20

Any idea when they'll fix Firefox so you can make streaming calls without turning your MBP into a toaster? 40x the battery usage vs. Safari when on a streaming call. It's so painful. Heh, literally. The machine gets too hot to hold comfortably. It's still my primary browser, but optimization is needed. Sucks to have to change browsers just to make calls. We live on streaming calls now. This has been an issue since at…

Post by dbg31415 » Mon, Jul 12, 2021, 3:01 PM UTC

da_chicken wrote: post #37

dbg31415 wrote: post #20

Any idea when they'll fix Firefox so you can make streaming calls without turning your MBP into a toaster? 40x the battery usage vs. Safari when on a streaming call. It's so painful. Heh, literally. The machine gets too hot to hold comfortably. It's still my primary browser, but optimization is needed. Sucks to have to change browsers just to make calls. We live on streaming calls now. This has been an issue since at…

You'll likely need a laptop CPU/GPU/APU, OS, browser, and site that natively support WebRTC and the media codec being used in hardware as much as possible. That's probably going to be AV1 support across the board for the foreseeable future. That's probably a couple years out. Real time AV codecs generally did not choose the "cheap" aspect of the "good / fast / cheap" triangle.