HTTP/1.1 was such a lovely protocol.
Firefox
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
- Firefox Customs: [email protected]
- Thunderbird: [email protected]
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
-
Always be civil and respectful
Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity. -
Don't be a bigot
No form of bigotry will be tolerated. -
Don't post security compromising suggestions
If you do, include an obvious and clear warning. -
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. -
Don't accuse others of shilling
Send honest concerns to the moderators and/or admins, and we will investigate. -
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.
@[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] 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] 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] "unship" is some microspeak-grade vernacular. They could have at least used "sink" or "scuttle".
@[email protected] Now a very niche feature. We probably do not know enough of its use in libcurl to rip it out as well?