Our views on the project are incompatible. I consider it harmful to the community to: - advertise fork as official continuation (the worst parts of this were eventually removed, but the project's website still completely mimics official and there's no indication it's a fork anywhere - ship binaries presumably made out of builds made by disappeared nofish - copypaste changes without attribution. Source: almost 2 years ago

Sure! Here are the domain links to the decentralized alternatives I mentioned: 1 Steemit: https://steemit.com/ 2 Mastodon: https://joinmastodon.org/ 3 Scuttlebutt: https://www.scuttlebutt.nz/ 4 ZeroNet: https://zeronet.io/ 5 Aether: https://getaether.net/ Please note that these links are current as of my knowledge cutoff in September 2021, and there's a possibility that the domains or... Source: almost 2 years ago

Https://zeronet.io/ (https://zeronet.io/) is 100% censorship proof. How come? Cause it is not centralized, It is 100% decentralized. Source: about 2 years ago

Https://zeronet.io/ is 100% censorship proof. Source: about 2 years ago

Nothing can be censored here. Nothing. https://zeronet.io. read that again. Nothing can be censored because it is 100% decentralized, that is the opposite of centralized power. Source: over 2 years ago

HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / 10 months ago

HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / almost 2 years ago

On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / about 3 years ago

To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 3 years ago

The program you are using to send data to the server may or may not automatically determine the right content-type header for your data, and knowing how to set and check headers is an essential skill. To learn more about the HTTP protocol check out the MDN guide or read the official standard, RFC 7230. - Source: dev.to / almost 4 years ago