Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
torsocks
Library to torify application - NOTE: upstream has been moved to https://gitweb.torproject.org/torsocks.git
The static blue background is missing. This might happen due to the following. The background is embedded in the html and sourced from a root-relative URL. Now, being a path-gateway, ipns-link.herokuapp.com requires the Referer header (with absolute URL) in the http request, so that it can resolve the PeerID when requested a relative path without the /ipns/PeerID prefix. Although the Gateway wants a complete referrer URL, the embedded tags may override it with a different ReferrerPolicy. If overridden in this way, the Gateway can't resolve the PeerID and fails. NOTE: this problem WILL GO AWAY once the IPNS-Link-GATEWAY supports wildcard subdomains, hopefully in the near future. Then, there wouldn't be any dependence on the Referer or cookie or server-side cache for resolving root-relative URLs, and everything would work as intended. Subdomain Gateway has always been the end-goal, but due to the lack of a domain I went with a path-gateway for prototyping.
Updated specs up for review. Requesting comments and discussion.
Also, when one can't access a website directly, because it is blocked in her country or due to some other reason, she can opt to access it using a gateway, provided the website has been exposed using IPNS-Link. (Compare Tor and VPN). Here too the gateway behaves as a forward proxy.
If you like this project, here's a list of things you can help with. Be a part of IPNS-Link and contribute however you see fit.