against using user@host identifiers
ken.horn at clara.co.uk
Fri Jun 3 01:48:35 PDT 2005
If we can standardise on a consumer using the same form name and/or
field name/attribute for the openid url field, then
bookmarklets/greasemonkey can help for the filling in.
My 2p is that urls are fine. If yours is too long / difficult, then
arrange to get a simpler one -- plenty of openid servers will provide
something short like user.myopenid.org. I don't think it's worth
worrying about right now.
Ask Bjørn Hansen wrote:
> On Jun 2, 2005, at 18:22, Xageroth Sekarius wrote:
>> This only changes one thing: the user must use whatever identity
>> services their host uses. That may seem like a downside but really,
>> it's a non-issue. First of all, it will be a rare case that a
>> LiveJournal user will not want to use LiveJournal's identity services.
>> Secondly, even if they do wish to use an alternate service, it would
>> be bizarre for them to use LiveJournal as their identifier at that
> Their web service might not have an identity server. Think blogspot
> user able to edit templates.
> For the user[@~]identifier thing: If we stick to just using the users
> URL we are sure the user can enter and remember all the characters
> - ask
More information about the yadis