7 ms·
Sourcehut will not blacklist the Go module mirror
- dang 4y agoRecent and related: Sourcehut will blacklist the Go module mirror - https://news.ycombinator.com/item?id=34310674 https://news.ycombinator.com/item?id=34310674 - Jan 2023 (337 comments)
- frankjr 4y agoSee, it is possible to make Google do some changes. You just have report the issue, wait a year, get banned, write a blog post, wait another year, and announce a block of their service. Easy.
- ocdtrekkie 4y agoAnd you have to be large enough or known enough in the first place that Google cares whether or not you block their service. ;)
- taviso 4y ago[flagged]
- ocdtrekkie 4y ago[flagged]
- deleted 4y ago[deleted]
- tptacek 4y agoIt does not appear to be the case that he was banned for anything about this issue.
- cycomanic 4y agoNobody knows exactly why he was banned (except for the people banning him), because the ban was not communicated to him or anyone else (at least according to his words). However, he did get banned after putting the issue into the golang issue tracker, so there is at least a temporal correlation.
- tptacek 4y agoThis was discussed in detail on the last DeVault thread. I don't think he wants it recapitulated here.
- throwaway2202 4y agoWhy call it temporal correlation when it neither denies nor establish causation? what can establish causation in this case? Unless one attempt to go back in time, recognize he is not banned yet he has put an issue in the tracker. Source hut requests were denied as would be expected from a corporate machine. Now the machine realized it should do damage control. we can repeat this test and check for causation where corporations do damage control without the need for time travel.
- Gigachad 4y agoDidn't google offer to immediately fix the issue for Sourcehut as a quick fix until they got the full fix out, and Drew declined stating Google needs to either fix the problem entirely or be blocked?
- 2h 4y agothats a cop out. If he accepted the quick fix, then Go team could just say "well it works for him, so now we dont need to do the full fix", or maybe they decide to slow play it. It was nearly two years, enough is enough.
- tptacek 4y agoIs that actually true? Does the timeline of the change the Go team is rolling out corroborate the claim?
- 2h 4y agodid you read the update to the article, as it answers that question
- tptacek 4y agoCan you be more specific? Is it updated in multiple places?
- philosopher1234 4y agoRuss commented in the original discussion that there was planned work to address Drew's issue (and more). From the update in this article, it appears that Drew is referring to that work. There is no indication in what I have read that the timeline for it has changed due to this drama.
- nerdponx 4y ago"Planned work" could mean it's sitting on an issue tracker somewhere, perpetually getting pushed back, because it's low priority and/or because someone actively doesn't want it to happen.
- MaxBarraclough 4y agoDon't forget the all important Hacker News front page step.
- 2h 4y ago[flagged]
- morelisp 4y agoSince -reuse was added in August and originally planned much earlier, it's unclear what Drew actually did, if anything, to speed this up. In the meantime, he has opted to... only solve the problem (if such a problem exists) for only SourceHut.
- 2h 4y agodid you read the update in the article? The Go team contact him directly and in private, as well as accepted responsibility for the situation regarding all small sites, not just SourceHut. So his actions did have an impact.
- morelisp 4y agoI did read it. I also read Go 1.19's release notes when they came out. I also read rsc's reply to the original post. I cannot figure out how Drew went back in time to add -reuse to Go 1.19 and proxy improvements to the Go team's schedule prior to the Go team contacting him in private.
- 2h 4y ago> Drew went back in time to add -reuse to Go 1.19 and proxy improvements to the Go team's schedule where did anyone say that?
- 8organicbits 4y agoI'd be super curious to see what load GitHub was seeing from this. There's a lot of focus on protecting smaller sites (who presumably have less funding) but the amount of redundant network traffic this generates must be quite large for other sites as well. I'm also still questioning the need for the proxy in the first place.
- notpushkin 4y agoI think GitHub is special-cased somehow.
- arp242 4y agoThe source for the proxy isn't available, but I'd be surprised if this was the case, based on what the Go team has written about this issue. They made some changes to allow excluding sites from refresh traffic in 2021 in response to this issue, but no mention of throttling or anything else. And if GitHub is special-cased, I don't see why any other site can't be special-cased either.
- rakoo 4y ago> The Go team has decided that the automatic refresh behavior is their responsibility, not the responsibility of other operators I am stunned it took so much kerfuffle to get there. Why is it not the default behavior ?
- deleted 4y ago[deleted]