I disagree with this completely. Libraries are cached by the Google proxy thing anyway, so as long as you have the correct commit you'll get the correct package even if GitHub goes down or bans the package.
I think version numbers are stupid anyway and people should be versioning based on exact hashes or commit ids, and I think go mod should default to working with exact commits and forget about versions. This would solve many problems.
Including the problem of migrating a package from a github namespace to your own domain namespace. Everything is a breaking change anyway.
But using custom domains is a stupid idea. These people that write these articles live in a fantasy land where everybody is supposed to have their own domain. In practice owning a domain is just an expensive status play conscientious people shouldn't be encouraging the cult of the custom domain.
I also think the article is written in a very poor and confusing way.
I also don't know how Nostr can fix this issue. In fact I think that someone could provide "free golang namespaces for ngit packages" like I do for mine, but more generic. For example, "nostr.technology/npub1.../packagename' could redirect to that package on NIP-34. This just piles up on the GitHub namespacing problems, but because I don't think those are real problems maybe I'll offer this service.
fiatjaf
npub180…jh6w6
2026-09-28 21:39:01 UTC
in reply to nevent1q…em33
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2026-09-28 21:39:01 UTCEvent JSON
{
"id": "de1c44a2c0b7ed61222c0b0fee78e70861d58a76d58fda91bfeb36f1ba2e3755",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1790631541,
"kind": 1111,
"tags": [
[
"I",
"https://iain.rocks/blog/dont-couple-your-go-code-to-github"
],
[
"K",
"web"
],
[
"e",
"b0dd3262d82f427bfbed9204d83514e0543eda784a5e3aedb51e68180ee87e2c",
"",
"46f3c7bb33cc3019049b76dc89dbb96e34c247bdda68b6ad8632682793ff8a1a"
],
[
"k",
"9802"
],
[
"p",
"46f3c7bb33cc3019049b76dc89dbb96e34c247bdda68b6ad8632682793ff8a1a"
]
],
"content": "I disagree with this completely. Libraries are cached by the Google proxy thing anyway, so as long as you have the correct commit you'll get the correct package even if GitHub goes down or bans the package.\n\nI think version numbers are stupid anyway and people should be versioning based on exact hashes or commit ids, and I think go mod should default to working with exact commits and forget about versions. This would solve many problems.\n\nIncluding the problem of migrating a package from a github namespace to your own domain namespace. Everything is a breaking change anyway.\n\nBut using custom domains is a stupid idea. These people that write these articles live in a fantasy land where everybody is supposed to have their own domain. In practice owning a domain is just an expensive status play conscientious people shouldn't be encouraging the cult of the custom domain.\n\nI also think the article is written in a very poor and confusing way.\n\nI also don't know how Nostr can fix this issue. In fact I think that someone could provide \"free golang namespaces for ngit packages\" like I do for mine, but more generic. For example, \"nostr.technology/npub1.../packagename' could redirect to that package on NIP-34. This just piles up on the GitHub namespacing problems, but because I don't think those are real problems maybe I'll offer this service.",
"sig": "9e997de03e70ce98bf15c29053706342035049597670c39269103153e9432136df64647480ad55da8c694ff703cb0cc237607d01a7555bf00acd93ab19d5f192"
}