Profiling registration forms that take either email OR phone number

[stuartpb]

Basically, Facebook's registration form has a double-field that can be either your email address or a phone number. Only one is required, but you do have to enter it twice (unlike the password, which you only enter once).

Maybe there should be a registration.form.contact with an accepts (and a corresponding repeat) that can act as an alternative to registration.form.email and/or registration.form.phone?

[stuartpb]

Putting this on the "future" milestone because I'm not certain I want to undermine registration.form.email this way so soon after establishing it.

[stuartpb]

Honestly, because this is pretty much unique to Facebook... hm. I'm thinking this might just mean registration.form has to have a notes (or caveats) that explains this.

[stuartpb]

Twitter has the same "phone or email" input, so I think it's worth figuring out.

[stuartpb]

Moving this to v0.1.0 because, yeah, I don't want Facebook and Twitter to ship with a major component of their registration undefined like this.

[stuartpb]

Eh, Facebook has email listed as a required input, and Twitter's registration is weird and not-easily-deterministic (varies depending on outside factors like having had a registration originate from your IP address recently) and multi-phase anyway (and the contact aspect is described in a note), so I think I can accept having these be a little under-served until v0.2.0.