I2P Reviews

HTTP Reviews

I2P mentions (48)

• SSL certificate expired

  The SSL certificate of https://download.i2p2.no expired on 29.08.2023. Therefore no downloads from the official https://geti2p.net site are available over https. Is this problem known? Source: almost 2 years ago

• RARBG is down and out!?

  They probably got harassed and don't have the man power to act. Great moment to give I2P https://geti2p.net/en/ a look as a viable alternative for torrents. Some clients already support both systems. Source: about 2 years ago

• Ask HN: What Are Alternatives to the Internet?

  There's a few abstractions of the web you can use today. https://freenetproject.org/ https://geti2p.net/en/ https://www.gnunet.org/en/ https://www.ipfs.tech/. - Source: Hacker News / about 2 years ago

• YOUR OPSEC SUCKS | UHQ SCHIZOID OPSEC GUIDE | BECOME BULLETPROOF

  Aside from being very secure, it will also be much faster than Tor overall. The best way to explain I2P is as a internet within an internet. One thing to mention is I2P does not hide the fact you are using the service at all. If you don't like Tor for some reason, this is another option to check out. I2P Link: https://geti2p.net/en/. Source: about 2 years ago

• Reddit tells court: Film studios spewed “nonsense” in demand for users’ names

  If you really want to go down that route, I2P is probably your best bet these days. https://geti2p.net/en/. Source: over 2 years ago

HTTP mentions (8)

• State management in Svelte apps

  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 / 11 months ago

• Evolving the Web: Discovering the History of HTTP Versions

  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

• Poll: Are client web requests sent to upstream servers or downstream servers?

  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

• How to cache TCP, SSL handshake on ALB?

  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

• HTTP Protocol Overview

  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