-
Notifications
You must be signed in to change notification settings - Fork 41
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
In the UI warn the user if they are not using well behaved TLD #440
Comments
Especially TLDs held by the same organization as .xyz should be blacklisted. |
Think this is obviated by the API rotation PR and since we're pushing that as the recommended action if their TLD messes with them. Closing |
Rotation is still a pita, especially if the user is on a 3rd party hoster. I think it's still worth it. |
What specifically should we warn here and where should I put the warning? It's an env config, should I pop up the error every time they login or just like hide the warning in danger zone? not sure there's any good place to put this. Maybe a warning only in the setup steps like just show a banner over the RoleSelector saying that their dns sucks? |
Yep, that's what I thought. |
When the guardian pastes in their domain that is not in org, com, info and possibly some other reputable TLDs, display warning message that some TLDs are know to ban domains for no good reason, and it will render affected peer unusable.
The text was updated successfully, but these errors were encountered: