@iliana Sadly I don't think Go people have any real recovery from this; loss of domain name control is fatal in the current package import model. The only option is to move your package to another domain, which renames it, and then get everyone to change import paths ('good luck with that' until builds start breaking someday).
Maybe this inet.af situation will push Google/Go to build some sort of actual solution, but I suspect not.