Comment by janandonly | Hacker News Reader

Comment by janandonly | Hacker News Reader

So basically CURL will get support for IPFS by using a proxy service (which is bad for user privacy).

And said proxy could bounce your request around for max 30 hops before a random IPFS-proxy honors the request. This is horrible for user privacy.

Brave browser [1] at least has a native support for IPFS and no need for proxies at all.

  >  Other IPFS privacy concerns: Brave, the browser, has actual native IPFS support (not using any gateway) and they have an informative page called How does IPFS Impact my Privacy?

[1] https://brave.com/brave-integrates-ipfs/

This blog post about cURL is saying that they will not do this, and will require a manual configuration of a gateway.

> By default, Brave will load the URI being requested via a public HTTP gateway; however, it will also show an infobar that asks you if you’d like to use a local node to resolve IPFS URIs.

So Brave by-default uses a public gateway.

> And said proxy could bounce your request around for max 30 hops before a random IPFS-proxy honors the request. This is horrible for user privacy.

It literally says: I have insisted, in the PR for ipfs support to curl, that the IPFS URL handling code should not automatically follow such gateway redirects, as I believe that adds even more risk to the user so if a user wants to allow this operation, it should be opt-in.

Max redirs in curl defaults to 50. Most browsers default to around 20. 30X (in the article) is a range of status response codes. You would probably benefit by rereading the article.

Reply on news.ycombinator.com