Hacker News Reader

Comment by tptacek | Hacker News Reader

You can phone anywhere you want; the proxy is configurable, and there are (from what I can see) several independent implementations of the proxy itself. Go defaults to Google's proxy; few people change the default because Google's proxy is very good.

View on HN

> Go defaults to Google's proxy; few people change the default because Google's proxy is very good.

What percentage of users do you think actually know that the proxy is even there?

This article strongly suggests Google's proxy is not "good", even if it "works". It sounds atrociously inefficient.

It brings a lot of security to the Golang dependency system. It is more than just a dumb proxy or cache

Smarter than your average proxy, but apparently dumb enough it doesn't actually cache at all, according to the reports.

Obviously it does cache, because the simplest solution offered by the Go team is to exclude sr.ht from the cache refresh that DeVault is complaining about, and he hasn't taken them up on that.

If it's such a widespread problem that there is a process to exclude domains from the cache refresh, doesn't that point to it being an issue that should be fixed by the party responsible instead of everybody else separately?

So far as I know, DeVault and the one other person who chimed in on his ticket are the only people who have ever availed themselves of this process, which may well have been created specifically for them. So, no, I don't think that's a valid point. Also: it is being fixed by the party responsible.

was being fixed. They just marked the issue as resolved and blocked any more comments on the thread.

They closed for comments because they started getting toxic, such is the modern internet mob mentality

Reply on news.ycombinator.com