> The concern raised here is more that things only work because the proxy masks problems. But making the modules available in the face of upstream breakage is

> The concern raised here is more that things only work because the proxy masks problems. But making the modules available in the face of upstream breakage is a point of the proxy. I can still build when GitHub is down. I can still get the version of the source I expected when upstream rebases or retags. Those are reasonable defaults. And with one env var I can also turn that off and check that the upstream is still as I expect. > Also alluded to is that said default proxy is kind of awful to its upstreams This is debatable; sr.ht seems to want to host a lot of go repos but not have people pull a lot of go repos. I'm not sure that's a case worth catering too.