On Wed, Mar 23, 2011 at 9:35 PM, Daniel Danilatos <[email protected]>wrote:
> Currently, ParticipantId contains an email address. This is not a > stable long term identifier for a user, and can cause problems. For > example, let's say "Bob Smith" [email protected] leaves the > organisation, and then someone else "Bob Jones" takes over the same > address [email protected]. Jones could then potentially gain access to > Smith's waves. > The problem is that any identifier needs to be human readable. The blah@blahapproach that has been borrowed from email actually works quite well. In terms of dealing with naming collisions, people have been dealing with it for many years now in email, IM and other fields. For instance in your example above, if there was an existing "[email protected]" for Bob Jones and Bob Smith comes along, Mr Smith would simply be given "[email protected]" or some other variation on the name. Generally I think we should leave this bit up to the admins who, being used to sorting this out will no doubt already have naming conventions for their users (Generally 2, one they use publically and one they use privately). -- James Purser Collaborynth http://collaborynth.com.au Mob: +61 406 576 553 Wave: [email protected]
