Ralf said:

> Maybe we can create a configurable template for user creation via
> mailgw. This could add a prefix or suffix and/or mandate the use of the
> full email address for the username. I think many web services today use
> the email address for good reasons...

There is a patch that allows somebody to login using their primary or secondary
email address (https://wiki.roundup-tracker.org/LoginWithEmail).

However, we don't obscure the username in templates etc. If we used email as username we
would need to do something to the templates (or the plain() method at least) to obscure/
filter an email address used as a username.

> > [rouilj]
> > So one addition to schema.py 'fixes' all the references he has to the
> > user class.
>
> It has other problems, though, in the API you can no longer search for
> user IDs when this is turned off.

Could you describe this issue more? How does setting a properties' try_id_parsing
prop affect searching? Wouldn't the filter spec property name:
    id=12345
vs.
    username=12345

cause try_id_parsing to be skipped as id only accepts id's and username only supports names?
You don't have the ambiguity in the API that you do in the edit field in the web interface.

-- rouilj

(P.S. The umlauted o in William's last name is tripping the unicode failure.)