Re: [ogpx] A Review of Multi-Domain Use Cases [Was: Re: OpenID and OGP : beginning the discussion ...]

[Carlo Wood <[e-mail]>]

On Mon, Jun 29, 2009 at 07:51:09AM -0700, Meadhbh Siobhan wrote:
> the second one is left as an exercise to client application developers
> and is analogous to the difficulty end users may have in
> differentiating two entities with the same name but distinct email
> addresses.

Well, then I'm almost satisfied :).

There is still one problem however. Before the application developers
can do this, they need to receive some globally unique identifier
that is always the same (ie, an email address, but again, I REALLY
don't want to share my email address with people online).

Example, a viewer is connected and the corresponding agent resides
in a given region. There it meet another avatar. In order to display
the tag above this new avatar the viewer needs to receive Firstname
Lastname... but, as I've tried to argue so far, it ALSO needs to
receive a globally unique identifier that uniquely identifies the
person behind the avatar (or rather, his account) and please don't
let it be an email address ;).

The point being: the server-client *protocol* needs to be designed
such that this globally unique ID is made available to all viewers.

If this is the case, then I'm happy and there should be no problems
in the future regarding this. If no separate ID is provided then
several problems occur:
* Impersonation (people deliberately using the same shape and skin etc)
* IM's will be logged to the same file, because the viewer can't
  know who is who.

Also, the ID has to be same every time - because the viewer will
need to recognize that this John Smith is not AGAIN a new one,
but the same, every time.

-- 
Carlo Wood <[e-mail]>