On talk.maemo.org, I'm known as pelago. On the main maemo.org site, I appear as John Veness (e.g. on brainstorm entries). On wiki.maemo.org I'm pelago again. On bugs.maemo.org I'm known by my email address without full name or nickname appearing, so that's a third identifier!

Can this be standardised across all parts of maemo.org?

http://wiki.maemo.org/Task:Single_sign-on

Thanks. I'm aware of that task (which will be very welcome when it happens). However this thread was more about the presentation of identity to other users. SSO in itself doesn't necessarily mean that different parts of maemo.org won't still use nickname sometimes, fullname other times, and email address yet more times. Furthermore, changing the presentation of identity doesn't even require single sign-on to be implemented.

You are correct, up to a point. SSO, in itself, wouldn't actually solve the multiple identity issue, if the SSO solution were to be implemented as just that, an SSO portal around all the Maemo applications.

That being said, I believe the current focus (which would make a lot more sense) would be to create a portfolio of applications which would be able to leverage one single identity store. Doing so, there would be no discrepancy between the different identities, and when an application looks in its Identity Store for "displayable name for user:...", it would get a single answer.

That being said, even having a single repository for all of the identities, this still doesn't mean that the applications would show every single field correctly. The matter of fact is that each component is being re-used, and nothing has been tailor-made (well, roughly speaking) for this project. As such, it is to be expected that different applications, from different origins, display different kinds of information.

I believe this is something that will be changed and adapted moving forward, however, there is quite a bit of work involved, and I don't believe it is one of the most urgent ones.

pelago it is a known issue, and some people who are very careful with their identity find it really bothersome.

However CrashandDie is on the right tracks. It's not an easy thing. Getting SSO is hard enough, but changing how different applications want to present the user would mean a lot more work. We really don't want to be running custom patched versions of all the services.