-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace broken links #2360
base: main
Are you sure you want to change the base?
Replace broken links #2360
Conversation
I feel like it would be better to find the updated pages instead of immediately switching to the IANA links, like I did in my previous PR. |
That approach works for me as well. This PR follows dnsguru's suggested method, which involves replacing them with IANA database links. The reasoning is probably that all registry websites are sourced from and should be sourced from the IANA page anyway. However, I replaced only broken links in this PR, as I do not think we should replace all functional URLs with IANA pages or remove "see also" lines, as these comments could often be valuable documentation. They can help future maintainers understand the nuances of different TLDs or special cases. Whether these are included as comments in the list or elsewhere, the documentation and links to specific registry rules are nice to have. |
So, it comes down to choosing between two directions:
The first approach benefits documentation but might burden volunteers, while the second places responsibility on the registries, which is probably the ideal situation. |
2. seems good for now. However I think if any volunteers have the free time and want to do so, I think they should be able to update the entries with registry links (maybe limit of 1-2 per section to prevent as much overhead as possible). |
This PR replaces all broken ccTLD links with IANA page links to resolve #2338