
HTTP
ZeroNet
thttpd
mini_httpd
micro_httpd
Solid
Gopher
Named Data Networking Project
IPFS
FileCoin
Dropbox
Syncthing
ownCloud
Google Drive
Nextcloud
Mega
HTTP
IPFSBased on our record, IPFS seems to be a lot more popular than HTTP. While we know about 292 links to IPFS, we've tracked only 9 mentions of HTTP. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months 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 / about 2 years 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 3 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 / over 4 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 4 years ago
IPFS and Filecoin exist to solve this problem. https://ipfs.tech. - Source: Hacker News / 10 months ago
IPFS: The Foundation of Decentralized Storage The InterPlanetary File System (IPFS) is a peer-to-peer hypermedia protocol designed to make the web faster, safer, and more open. It's indispensable for storing large files and static assets for your dApps in a decentralized and censorship-resistant manner, referencing content by its hash. Store with IPFS. - Source: dev.to / about 1 year ago
WeaveChain will be a CosmosSDK based DePIN blockchain and a marketplace to match database developers / dapps with rollup operators. It's basically a Filecoin for database. zkDB/WeaveDB is to WeaveChain as IPFS is to Filecoin. We will introduce 2 unique components to connect with real-world data and web2. - Source: dev.to / about 1 year ago
IPFS (optional: if you want to run your own IPFS node). - Source: dev.to / about 2 years ago
When I click on https://synapsemedia.io/ I get redirected to a link like https://ipfs.io/ipns/synapsemedia.io (to use ipfs.io instead of my local node). Source: over 3 years ago
ZeroNet - ZeroNet. Open, free and uncensorable websites, using Bitcoin cryptography and BitTorrent network. Download for Windows 9. 6MB ยท Unpack ยท Run ZeroNet. exe.
FileCoin - Filecoin is a data storage network and electronic currency based on Bitcoin.
thttpd - thttpd is a simple, small, portable, fast, and secure HTTP server.
Dropbox - Online Sync and File Sharing
mini_httpd - mini_httpd is a small HTTP server for low or medium traffic sites.
Syncthing - Syncthing replaces proprietary sync and cloud services with something open, trustworthy and...