> the ban prevents me from discussing the matter further Hi ddevault, FWIW, in May 2022 on that #44577 issue [0] you had opened, it looks like someone on the c

> the ban prevents me from discussing the matter further Hi ddevault, FWIW, in May 2022 on that #44577 issue [0] you had opened, it looks like someone on the core Go team commented there [1] recommending that you email the golang-dev mailing list or email them directly. Separately, it looks like in July 2022, in one of the issues tracking the new friendlier -reuse flag, there was a mention [2] of the #44577 issue you had opened. In the normal course, that would have triggered an automatic update on your #44577 issue... but I suspect because that #44577 issue had been locked by one of the community gardeners as "too heated", that automatic update didn't happen. (Edit: It looks like it was locked due to a series of rapid comments from people unrelated to Sourcehut, including about “scummy behavior”). Of course, communication on large / sprawling open source projects is never quite perfect, but that's a little extra color... [0] https://github.com/golang/go/issues/44577 https://github.com/golang/go/issues/44577 [1] https://github.com/golang/go/issues/44577#issuecomment-1137822116 https://github.com/golang/go/issues/44577#issuecomment-11378... [2] https://github.com/golang/go/issues/53644#issuecomment-1175117527 https://github.com/golang/go/issues/53644#issuecomment-11751...