Live data from Hacker News

Hostnames and usernames to reserve

ldpreload.com

11–20 of 25 posts

Re: Hostnames and usernames to reserve

#11
post #7

When github used to host "pages" under github.com I remember registering "blog.github.com" (and reporting obviously). If you take the social-engineering into account the list should be made long: login, support, status, help, ... Just to say, the list could be made much longer (eg: login)

Seems PayPal also missed this memo: https://www.paypal.me/support https://www.paypal.me/download https://www.paypal.me/signup

Re: Hostnames and usernames to reserve

#12
I would suggest adding "autodiscover" to the list of disallowed hosts. It is used by Microsoft Outlook and Exchange ActiveSync clients (e.g. in smartphones) to automatically detect the correct server settings.

Re: Hostnames and usernames to reserve

#13
post #5

Earlier quoted context omitted.

Email addresses and domain names are case-ignoring so you should never allow usernames that differ only in case. Allowing only lower case is an easy way to do this.

The username part of an email address can actually be case sensitive, and this has been known to cause problems with some systems (e.g. https://airmail.tenderapp.com/help/discussions/287/113-case-... ).

So instead of converting to lowercase, store them with case preserved but do a case insensitive uniqueness check (and probably allow any case for login).

Re: Hostnames and usernames to reserve

#16

Earlier quoted context omitted.

The username part of an email address can actually be case sensitive, and this has been known to cause problems with some systems (e.g. https://airmail.tenderapp.com/help/discussions/287/113-case-... ).

So instead of converting to lowercase, store them with case preserved but do a case insensitive uniqueness check (and probably allow any case for login).

or just force all lowercase and keep the support burden lower and save yourself a ton of trouble when dealing with foreign systems. Add a rule on incoming e-mail to convert all addresses for the local domain to lowercase to complete the package.

Re: Hostnames and usernames to reserve

#18

Earlier quoted context omitted.

The username part of an email address can actually be case sensitive, and this has been known to cause problems with some systems (e.g. https://airmail.tenderapp.com/help/discussions/287/113-case-... ).

So instead of converting to lowercase, store them with case preserved but do a case insensitive uniqueness check (and probably allow any case for login).

Yes, this seems to be the right behavior for case-insensitive things like DNS names as well. If a user inputs one, preserve the case when you store it, but do case-insensitive comparisons.

Re: Hostnames and usernames to reserve

#19

Earlier quoted context omitted.

So instead of converting to lowercase, store them with case preserved but do a case insensitive uniqueness check (and probably allow any case for login).

or just force all lowercase and keep the support burden lower and save yourself a ton of trouble when dealing with foreign systems. Add a rule on incoming e-mail to convert all addresses for the local domain to lowercase to complete the package.

It probably depends on whether we're talking about making your own users, like the original link, or allowing users to interface with other systems, like entering an email address.

Re: Hostnames and usernames to reserve

#20
post #11
post #7

When github used to host "pages" under github.com I remember registering "blog.github.com" (and reporting obviously). If you take the social-engineering into account the list should be made long: login, support, status, help, ... Just to say, the list could be made much longer (eg: login)

Seems PayPal also missed this memo: https://www.paypal.me/support https://www.paypal.me/download https://www.paypal.me/signup

Here are some that I've reserved for my own web app, now inclusive of RFC 2142:

https://gist.github.com/zachrose/30862a11857a31242d60

Post reply on HN