this post was submitted on 06 Sep 2024
2 points (100.0% liked)

Firefox

68 readers
1 users here now

The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.

You can subscribe to this community from any Kbin or Lemmy instance:

Related

Rules

While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.

Rules

  1. Always be civil and respectful
    Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.

  2. Don't be a bigot
    No form of bigotry will be tolerated.

  3. Don't post security compromising suggestions
    If you do, include an obvious and clear warning.

  4. Don't post conspiracy theories
    Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.

  5. Don't accuse others of shilling
    Send honest concerns to the moderators and/or admins, and we will investigate.

  6. Do not remove your help posts after they receive replies
    Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.

founded 1 year ago
MODERATORS
 

#Firefox joins the other browsers and disables HTTP/2 server push.

libcurl still supports it!

https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ?pli=1

top 8 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 1 month ago

HTTP/1.1 was such a lovely protocol.

[–] [email protected] 1 points 1 month ago (1 children)

@[email protected] I'm honestly amazed I haven't had the courage just to default that setting to off. It only surprises users.

[–] [email protected] 1 points 1 month ago (1 children)

@[email protected] in curl's case we only offer it via an API but that also means we cannot very easily take it away without risking hurting a few users... Ie we would need to bump SONAME.

[–] [email protected] 1 points 1 month ago

@[email protected] Oh sure, the same is true for Swift. The thing that I haven't done yet is change our default settings. Currently we leave SETTINGS_ENABLE_PUSH at their defaults, so "on" for clients. I'm wondering about just switching it off unilaterally.

[–] [email protected] 1 points 1 month ago

@[email protected] "unship" is some microspeak-grade vernacular. They could have at least used "sink" or "scuttle".

[–] [email protected] 1 points 1 month ago

@[email protected] WHYYYYY. Curse Chrome just deleting things for no reason

[–] [email protected] 1 points 1 month ago (1 children)

@[email protected] Now a very niche feature. We probably do not know enough of its use in libcurl to rip it out as well?

[–] [email protected] 1 points 1 month ago

@[email protected] right, presumably not widely used but we can't really tell...