Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sourcehut will blacklist the Go module mirror

sourcehut.org

Post reply on HN
Print view View original

21–30 of 365 posts

Re: Sourcehut will blacklist the Go module mirror

#21

Post by pjmlp »

leetrout wrote: post #8

I feel like Drew has been in a pissing match with the Go team for a while so this outcome doesnt surprise me. I love Go but not Google's stewardship of it. The tracking proxy, Russ' takeover / squash of the package management work, the weird silence / stonewalling on other community issues... Drew has a valid complaint. I hate to hear he was banned from the issue tracker but that sounds about right. As a sibling said…

Many issues with Go design steem from "how Google does it", this is just yet another one.

Re: Sourcehut will blacklist the Go module mirror

#22

Post by ComputerGuru »

Thaxll wrote: post #14
xenophonf wrote: post #11

This: > I was banned from the Go issue tracker without explanation, and was unable to continue discussing the problem with Google. is completely asinine. But it's also par for the course when it comes to interacting with Google. When is anyone going to hold them to account for their terrible customer service and community interaction?

It's one side of the story. I don't think he was banned for no reasons.

Knowing him, it probably wasn’t nothing. But that also does Dr matter - he runs a hosting service that sees a fair amount of traffic and the onus is on Google as stewards of the golang community and the brilliant minds behind invisibly proxing requests through Google’s servers to continue to figure this issue out. They have his email address.

Re: Sourcehut will blacklist the Go module mirror

#23

Post by pjmlp »

no_wizard wrote: post #17
leetrout wrote: post #8

I feel like Drew has been in a pissing match with the Go team for a while so this outcome doesnt surprise me. I love Go but not Google's stewardship of it. The tracking proxy, Russ' takeover / squash of the package management work, the weird silence / stonewalling on other community issues... Drew has a valid complaint. I hate to hear he was banned from the issue tracker but that sounds about right. As a sibling said…

What’s the deal on package mangement? They did quite a few iterations here so I don’t follow. Don’t know about the Russ takeover either

TL;DR version.

Go package management was quite poor for many real use cases outside Google, so the community railed around many competing proposals, and when it appeared there was a clear winner, the Go team came out with their own solution instead.

This after kind of supporting the ongoing community efforts.

Re: Sourcehut will blacklist the Go module mirror

#24

Post by ddevault »

Thaxll wrote: post #14
xenophonf wrote: post #11

This: > I was banned from the Go issue tracker without explanation, and was unable to continue discussing the problem with Google. is completely asinine. But it's also par for the course when it comes to interacting with Google. When is anyone going to hold them to account for their terrible customer service and community interaction?

It's one side of the story. I don't think he was banned for no reasons.

I would share their side as well, but I never heard it. This is a violation of their own code of conduct, which requires them to notify the affected person, explain why, and offer the opportunity to mediate the situation. This is not the first time I was banned from the Go community without notice or explanation, and the first time turned out to be frivolous -- the ban was overturned months later with an admission that it was never justified in the first place. Community management in Go strikes me as very insular and unprofessional.

Regardless, I don't really want to re-litigate it here. The main issue is that Google has been DoS'ing SourceHut's servers for two years, and I think we can all agree that there is no conduct violation for which DoS'ing your servers is a valid recourse.

Re: Sourcehut will blacklist the Go module mirror

#25

Post by xena »

pjmlp wrote: post #23
no_wizard wrote: post #17

Earlier quoted context omitted.

What’s the deal on package mangement? They did quite a few iterations here so I don’t follow. Don’t know about the Russ takeover either

TL;DR version. Go package management was quite poor for many real use cases outside Google, so the community railed around many competing proposals, and when it appeared there was a clear winner, the Go team came out with their own solution instead. This after kind of supporting the ongoing community efforts.

Even more fun, Google doesn't even use Go modules internally! They use their own homegrown build system abomination that requires teams of people to maintain.

Re: Sourcehut will blacklist the Go module mirror

#26

Post by Thaxll »

pjmlp wrote: post #23
no_wizard wrote: post #17

Earlier quoted context omitted.

What’s the deal on package mangement? They did quite a few iterations here so I don’t follow. Don’t know about the Russ takeover either

TL;DR version. Go package management was quite poor for many real use cases outside Google, so the community railed around many competing proposals, and when it appeared there was a clear winner, the Go team came out with their own solution instead. This after kind of supporting the ongoing community efforts.

And yet go mod is far superior to anything that was created before, having used dep which was honestly very slow and buggy, go mod works just fine and is one of the best pkg mgmt right now ( all languages included ).

Package managment should not be created and maintained outside of the core team, maybe the process in which they decided the solution was not the best but the end result speaks for itself, go mod is very good.

Re: Sourcehut will blacklist the Go module mirror

#27

Post by comex »

According to some comments in the linked GitHub issue, including [1] from last May, Drew could have simply asked to be excluded from automatic refresh traffic from the mirror. If I understand correctly, that would still leave traffic from the mirror when it’s acting as a direct proxy for someone’s request, but that is traffic that would be going to sr.ht regardless.

For some reason he did not do this and instead chose an option that causes breakage.

[1] https://github.com/golang/go/issues/44577#issuecomment-11378...

Re: Sourcehut will blacklist the Go module mirror

#28

Post by cp9 »

pjmlp wrote: post #23
no_wizard wrote: post #17

Earlier quoted context omitted.

What’s the deal on package mangement? They did quite a few iterations here so I don’t follow. Don’t know about the Russ takeover either

TL;DR version. Go package management was quite poor for many real use cases outside Google, so the community railed around many competing proposals, and when it appeared there was a clear winner, the Go team came out with their own solution instead. This after kind of supporting the ongoing community efforts.

frankly, go mod is a much better solution than dep ever was

Re: Sourcehut will blacklist the Go module mirror

#29

Post by [deleted] »

comex wrote: post #27

According to some comments in the linked GitHub issue, including [1] from last May, Drew could have simply asked to be excluded from automatic refresh traffic from the mirror. If I understand correctly, that would still leave traffic from the mirror when it’s acting as a direct proxy for someone’s request, but that is traffic that would be going to sr.ht regardless. For some reason he did not do this and instead chos…

[deleted]

Re: Sourcehut will blacklist the Go module mirror

#30

Post by numbsafari »

pdonis wrote: post #10
galleywest200 wrote: post #6

> It should not be necessary to fetch the same git module up to 2,000 times per day. Holy cow Google! Wouldn't it behoove us to check if any changes occurred before downloading an entire repo?

I don't understand why they have to do a fresh clone every time.

[flagged]
Post reply on HN