We need userame and email to build the basic user information, for example, user name is used in the URL. Could you suggest some wording to make it more clear?
> We need userame and email to build the basic user information, for example, user name is used in the URL.
If I'm not mistaken, entry of an e-mail address and a Diigo user name does _not_ prevent the strange behaviour. My recollection is that the _second_ requirement to log in to Diigo occurs immediately or shortly after successful entry of the information required by Diigo.
Certainly, though it can not be until I next induct an OpenID user to Diigo.
> thought it was fixed.
Approximately, when?
A glance at membership dates for a particular group suggests that 2008-10-20 was the last day on which I inducted someone (and we experienced the issue).
> A glance at membership dates for a particular group suggests that 2008-10-20 was the last day on >which I inducted someone (and we experienced the issue).
1. for a first ever log in to Diigo, use OpenID
2. follow the routine
3. a second log in is required
- *if* a log out has occurred, there's no obvious indication that it has occurred; just, a noticeable requirement to log in _twice_.
For users who are new to both OpenID and Diigo, this can be confusing.
----
Subsequent OpenID log-ins to Diigo seem to be fine.
Thanks!
In the meantime, a question: re http://www.diigo.com/profile/edit/basic
* if first name and last name are entered, is there no way of obscuring that information?
I see no padlock icon alongside those fields.
Some colleagues have chosen to
a) have an _obscure_ Diigo ID
and
b) _not_ enter their real names.
Whilst this may be contrary to the social aspect (less likely to find someone by name or ID) we should respect users' wishes.
I might suggest, adding a security option, so that real names can be disclosed only after Diigo friendship has been granted.
Thanks - Graham
If I'm not mistaken, entry of an e-mail address and a Diigo user name does _not_ prevent the strange behaviour. My recollection is that the _second_ requirement to log in to Diigo occurs immediately or shortly after successful entry of the information required by Diigo.
Thanks.
> Could you try it again when you have time?
Certainly, though it can not be until I next induct an OpenID user to Diigo.
> thought it was fixed.
Approximately, when?
A glance at membership dates for a particular group suggests that 2008-10-20 was the last day on which I inducted someone (and we experienced the issue).
That's right. We fixed it about 10 days ago.
Ah, thanks … sorry for not mentioning the (past) date of the issue when I opened this thread. It could have saved you some time! - sorry.
Postscript: http://groups.diigo.com/Diigo_HQ/forum/topic/suggestion-services-change-log-7473
To Top