Re: When choosing user names for websites, I prefer to use:

Many sites require an email-address as user-name, so I often don't have much choice.

I only can decide how important the site is, and if I want to get mails from it. For real important sites (like my bank) I use my "premium" address, for temporary important sites (eg for shopping, booking hotels etc.) I use my main address, and for others I use an address I only check once or twice a month.

And then there are sites where I use mailinator....

so long, Rata

Comment on Re: When choosing user names for websites, I prefer to use:

Replies are listed 'Best First'.
Re^2: When choosing user names for websites, I prefer to use: by chacham (Prior) on Jul 06, 2014 at 03:41 UTC
With google, i can use email+random@gmail.com. The random part is usually the site name. This lets me know who uses what email and possibly to block. The only place i have seen the + sign barred is Quicken for Mac 2015 Beta 4. (Beta 3 allowed it.) I also have my own domain. I use a subdomain, so email addresses are website@sub-domain.example.com. This works except when the site does not support subdomains, which is probably because somebody wrote his own non-rfc-compliant address validator. Sub-domain seem to be safe from brute force spam, as they send it to domains, not sub-domains.	[reply]

Replies are listed 'Best First'.

Re^2: When choosing user names for websites, I prefer to use:
by chacham (Prior) on Jul 06, 2014 at 03:41 UTC

With google, i can use email+random@gmail.com. The random part is usually the site name. This lets me know who uses what email and possibly to block. The only place i have seen the + sign barred is Quicken for Mac 2015 Beta 4. (Beta 3 allowed it.)

I also have my own domain. I use a subdomain, so email addresses are website@sub-domain.example.com. This works except when the site does not support subdomains, which is probably because somebody wrote his own non-rfc-compliant address validator. Sub-domain seem to be safe from brute force spam, as they send it to domains, not sub-domains.

[reply]