4 ms·

I had fun in the vmware-broadcom transition because the broadcom portal doesn't allow that, but the vmware portal did. Not even in my username, just in the sur

by soneil 2y ago

I had fun in the vmware-broadcom transition because the broadcom portal doesn't allow that, but the vmware portal did. Not even in my username, just in the surname field. The new portal ate it on that so hard, I wasn't even allowed to create a ticket to do anything about it. Not as bad as when I was once issued a first.o'last@corp email address though ..

mixmastamyk 2y ago
There may be a Unicode character that looks like apostrophe but has no quoting semantics. I use an arrow instead of greater-than symbol in my prompt for the same reason. To avoid copy/paste issues.
- jcranmer 2y ago
  Non-ASCII characters in email addresses have even worse compatibility issues than punctuation characters. Punctuation fails because people don't know the standard. Non-ASCII fails because people don't know the latest standard.
deltarholamda 2y ago
>Not as bad as when I was once issued a first.o'last@corp email address though Oh, man, that happened to me too, way back in the late 90s. I had forgotten about that. It broke things all over the place. Even now you run into the occasional validator that is convinced that the plus sign is not valid in email addresses.
- mschuster91 2y ago
  > Even now you run into the occasional validator that is convinced that the plus sign is not valid in email addresses. These are intentional IMHO - force people to use their actual email address so a potential breach can't be tied back to the service. That's the only reason why someone would use a + in the first place.
  - tolciho 2y ago
    Some validators are silly regular expressions that someone wrote in a minute without thinking about it ("Mastering Regular Expressions" has a regex associated with it for better matching an address; that regex is quite the sight to behold). And disallowing + is a crummy solution to whatever "force people to use their actual email address" means given that someone with full control of a domain can invent the alias whatevertheywant@example.org instead of using something with a + in it, or they can spin up an alternate address on some alternate provider, etc. Other reasons folks use + in their email is to do mail routing (except where crappy web services disallow the + because they relied on a crappy regex) but then again I have no idea what "potential breach can't be tied back to the service" is meant to mean.
    - mschuster91 2y ago
      > but then again I have no idea what "potential breach can't be tied back to the service" is meant to mean. Easy. Say I subscribe as "username+servicename@gmail.com" everywhere, when I get spam at that email address that service must have been either breached or sold off my data.
  - jonathanlydall 2y ago
    More likely just a default. I built the authentication system on our website and as a regular user of Gmail + aliasing I was very surprised when my brother pointed out our website didn’t allow them. Turns out the default for Microsoft’s ASP.NET Identity Framework is to disallow special characters, but simply setting a flag in its configuration rectified this.

by soneil 2y ago

mixmastamyk 2y ago

There may be a Unicode character that looks like apostrophe but has no quoting semantics. I use an arrow instead of greater-than symbol in my prompt for the same reason. To avoid copy/paste issues.

jcranmer 2y ago
Non-ASCII characters in email addresses have even worse compatibility issues than punctuation characters. Punctuation fails because people don't know the standard. Non-ASCII fails because people don't know the latest standard.

deltarholamda 2y ago

>Not as bad as when I was once issued a first.o'last@corp email address though Oh, man, that happened to me too, way back in the late 90s. I had forgotten about that. It broke things all over the place. Even now you run into the occasional validator that is convinced that the plus sign is not valid in email addresses.

mschuster91 2y ago
> Even now you run into the occasional validator that is convinced that the plus sign is not valid in email addresses. These are intentional IMHO - force people to use their actual email address so a potential breach can't be tied back to the service. That's the only reason why someone would use a + in the first place.
- tolciho 2y ago
  Some validators are silly regular expressions that someone wrote in a minute without thinking about it ("Mastering Regular Expressions" has a regex associated with it for better matching an address; that regex is quite the sight to behold). And disallowing + is a crummy solution to whatever "force people to use their actual email address" means given that someone with full control of a domain can invent the alias whatevertheywant@example.org instead of using something with a + in it, or they can spin up an alternate address on some alternate provider, etc. Other reasons folks use + in their email is to do mail routing (except where crappy web services disallow the + because they relied on a crappy regex) but then again I have no idea what "potential breach can't be tied back to the service" is meant to mean.
  - mschuster91 2y ago
    > but then again I have no idea what "potential breach can't be tied back to the service" is meant to mean. Easy. Say I subscribe as "username+servicename@gmail.com" everywhere, when I get spam at that email address that service must have been either breached or sold off my data.
- jonathanlydall 2y ago
  More likely just a default. I built the authentication system on our website and as a regular user of Gmail + aliasing I was very surprised when my brother pointed out our website didn’t allow them. Turns out the default for Microsoft’s ASP.NET Identity Framework is to disallow special characters, but simply setting a flag in its configuration rectified this.