OpenID - LiveJournal
Mio
I'd like to ask smth about OpenID Wordpress plugin
I think it would great if it will support LiveJournal.com OpenId
as smth unique. The point is LiveJournal is very popular in Russia. On
the other hand very small amount of people really knows what OpenID
is.
It would be cool if author will see LJ icon after comment posting
instead of OpenID icon and if LJ avatars will be used when LJ openid
used.
Also I can make Russian translation for OpenID plugin so please send
me some .po :) igor (wow) denisov.eu
---
Igor
Chris Messina
Chris Messina
Citizen-Participant &
Open Technology Advocate-at-Large
factoryjoe.com # diso-project.org
citizenagency.com # vidoop.com
This email is: [ ] bloggable [X] ask first [ ] private
Игорь Денисов
OpenID is Livejournal ID and Yahoo ID. And in Russia we have 2 big local providers - Yarushka (http://wow.ya.ru) and MoiKrug.ru.
+1.That's a great idea.I've been thinking lately that we should basically do what Facebook is mandating for Connect-provided avatars (note the "f" icon in the bottom right):...that is, if someone signs in with an OpenID, we should leave a little icon in the corner of the avatar, like so:And for specific OpenIDs, like LiveJournal, Yahoo, AOL, etc... perhaps we could use a more specific icon?Chris
--
Игорь Денисов
http://socvestnik.ru/
http://denisov.eu/
Martin Atkins
> +1.
>
> That's a great idea.
>
> I've been thinking lately that we should basically do what Facebook is
> mandating for Connect-provided avatars (note the "f" icon in the bottom
> right):
>
> http://skitch.com/factoryjoe/62s5/fb-connect
>
> ...that is, if someone signs in with an OpenID, we should leave a little
> icon in the corner of the avatar, like so:
>
> http://skitch.com/factoryjoe/62ss/beau-openid
>
> And for specific OpenIDs, like LiveJournal, Yahoo, AOL, etc... perhaps
> we could use a more specific icon?
>
This does of course have the problem that we don't have a userpic
delivery mechanism for OpenID yet. There was a little talk recently
about extending SREG to have a "userpic URL" field, but I believe
Facebook provides resized userpics at a variety of standard sizes which
would be harder to achieve in OpenID land. (Can't guarantee without
fetching it what size userpic you've been linked to, no terms of service
regulating userpic content, etc.)
I think it's also worth considering what would be achieved by adding
such an icon. In the Facebook Connect user experience the icon tells you
something useful (I can also interact with this person on Facebook) but
I'm not sure than an OpenID icon has the same utility. It'd primarily
just be OpenID promotion.
Having a LiveJournal or MySpace icon would probably be more useful,
though. It depends really if people are using their LJ/MySpace accounts
primarily just as a general "I don't want another password" identifier
or whether they really are intending to assert "I'm user x at
LiveJournal". In the former case they might be quite surprised to have
their LiveJournal account called out. If it was initiated with something
saying "Connect your LiveJournal Account!" this maybe be less jarring.
(In other words, using the "Connect" branding to mean "Sign in and bring
your account with you" vs. "log in" meaning just "create a session here".
But before I go too far thinking I'm any sort of UI designer I'll stop. :)
Chris Messina
This does of course have the problem that we don't have a userpic
delivery mechanism for OpenID yet. There was a little talk recently
about extending SREG to have a "userpic URL" field, but I believe
Facebook provides resized userpics at a variety of standard sizes which
would be harder to achieve in OpenID land. (Can't guarantee without
fetching it what size userpic you've been linked to, no terms of service
regulating userpic content, etc.)
<link rel="pavatar avatar logo" href="http://factorycity.net/images/avatar.jpg" />
I think it's also worth considering what would be achieved by adding
such an icon. In the Facebook Connect user experience the icon tells you
something useful (I can also interact with this person on Facebook) but
I'm not sure than an OpenID icon has the same utility. It'd primarily
just be OpenID promotion.
In the former case they might be quite surprised to have
their LiveJournal account called out. If it was initiated with something
saying "Connect your LiveJournal Account!" this maybe be less jarring.
(In other words, using the "Connect" branding to mean "Sign in and bring
your account with you" vs. "log in" meaning just "create a session here".
Stephen Paul Weber
Hash: SHA1
> Heh. Well, I tried pushing this a long time ago. I'm using this in the head
> of factoryjoe.com, though no one supports it:
>
> <link rel="pavatar avatar logo"
> href="http://factorycity.net/images/avatar.jpg" />
hCard anyone? That's what diso-profile uses :)
> Obviously some sites are using the apple-touch-icon approach, so I think we
> should be liberal with what we look for when someone signs in (Gravatar
> being the first priority here) and perhaps give them the option to pick a
> photo or upload their own if they want (basically pick the best choose and
> then provide a Flickr-style drop-down: "Want to change this?").
Similar to what diso-profile does. hCard discovered photo or user added
photo first, gravatar second :)
- --
Stephen Paul Weber, @singpolyma
Please see <http://singpolyma.net> for how I prefer to be contacted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJSVlb6oSxepE9BOsRAmrKAJ0YXj5GP820t3g2p9c+hgKzxOy8nQCgyLgh
rP9bGmMfda148dXODhhiKVc=
=5t9r
-----END PGP SIGNATURE-----
Martin Atkins
>
> Heh. Well, I tried pushing this a long time ago. I'm using this in the
>
> <link rel="pavatar avatar logo" href="http://factorycity.net/images/avatar.jpg" />
>
> I think the Pavatar effort is silly, but we definitely need a convenient
> way to discover a userpic, ideally at different sizes (if only for
> efficiency's sake).
>
Looking at what folks have implemented, I think implementers definitely
prefer getting this stuff via SREG or otherwise in the OpenID
transaction rather than having to go do discovery separately. I don't
think many OpenID libraries make it easy to do this sort of thing
without doing an additional request or being clever with how you handle
caching. (Net::OpenID::Consumer for Perl will hand you RSS, Atom and
FOAF URLs in some cases, but not arbitrary stuff like that.)
Publishing an avatar link or a Microformats image could be useful for
other consumers though. I've currently got my photo in my hCard, though
right now I'm using a non-standard mechanism to mark my hCard as the
"representative hCard" so no parser can really see it.
Stephen Paul Weber
Hash: SHA1
> Publishing an avatar link or a Microformats image could be useful for
> other consumers though. I've currently got my photo in my hCard, though
> right now I'm using a non-standard mechanism to mark my hCard as the
> "representative hCard" so no parser can really see it.
What non-standard mechanism is that, and why don't you use the standard
one?
- --
Stephen Paul Weber, @singpolyma
Please see <http://singpolyma.net> for how I prefer to be contacted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJSWaF6oSxepE9BOsRAmigAKCW7ndgWgIcGWkZrbdTYsU9CzsXQQCg6Z1T
KE7qqvQB9Ptw34km9yl5Xco=
=8tId
-----END PGP SIGNATURE-----
Martin Atkins
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Publishing an avatar link or a Microformats image could be useful for
>> other consumers though. I've currently got my photo in my hCard, though
>> right now I'm using a non-standard mechanism to mark my hCard as the
>> "representative hCard" so no parser can really see it.
>
> What non-standard mechanism is that, and why don't you use the standard
> one?
>
In my head section I use:
<link rel="me" href="#contactinfo" />
(where #contactinfo points at the root element of my hcard)
I believe the standard mechanism is to create a hyperlink within the
hCard from my page to itself, which just seems weird to me.
Stephen Paul Weber
Hash: SHA1
> I believe the standard mechanism is to create a hyperlink within the
> hCard from my page to itself, which just seems weird to me.
There are two standard mechanisms... uid with value of the current page
(the one you reference) and also just having rel=me on any of the
class=url entries (which is more common).
Both of these are accepted by the socialsearchme crawler.
- --
Stephen Paul Weber, @singpolyma
Please see <http://singpolyma.net> for how I prefer to be contacted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJSWtl6oSxepE9BOsRAoLQAKDFdfZRXH3hLQR+aEEi5JWSgxjnhACff5LP
df0oLcNTDFItFzSSQrOe5YA=
=Vbvb
-----END PGP SIGNATURE-----
Martin Atkins
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> I believe the standard mechanism is to create a hyperlink within the
>> hCard from my page to itself, which just seems weird to me.
>
> There are two standard mechanisms... uid with value of the current page
> (the one you reference) and also just having rel=me on any of the
> class=url entries (which is more common).
>
> Both of these are accepted by the socialsearchme crawler.
>
I'm not sure I've followed this, since these both seem to involve the
page linking to itself...
If I'm publishing a representative hCard on http://martin.atkins.me.uk/,
then I would presumably need to have a link within my hCard like this:
<a href="http://martin.atkins.me.uk/" class="url" rel="me">
or, like this:
<a href="http://martin.atkins.me.uk/" class="url uid">
or have I missed something?
(Though I notice we're actually discussing this on diso-project rather
than on microformats; sorry for veering off-topic... I forgot what
mailing list I was reading. :) )
Chris Messina
hCard anyone? That's what diso-profile uses :)
> Heh. Well, I tried pushing this a long time ago. I'm using this in the head
> of factoryjoe.com, though no one supports it:
>
> <link rel="pavatar avatar logo"
> href="http://factorycity.net/images/avatar.jpg" />
Similar to what diso-profile does. hCard discovered photo or user added
> Obviously some sites are using the apple-touch-icon approach, so I think we
> should be liberal with what we look for when someone signs in (Gravatar
> being the first priority here) and perhaps give them the option to pick a
> photo or upload their own if they want (basically pick the best choose and
> then provide a Flickr-style drop-down: "Want to change this?").
photo first, gravatar second :)
Chris Messina
Stephen Paul Weber wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> I believe the standard mechanism is to create a hyperlink within the
>> hCard from my page to itself, which just seems weird to me.
>
> There are two standard mechanisms... uid with value of the current page
> (the one you reference) and also just having rel=me on any of the
> class=url entries (which is more common).
I'm not sure I've followed this, since these both seem to involve the
page linking to itself...
If I'm publishing a representative hCard on http://martin.atkins.me.uk/,
then I would presumably need to have a link within my hCard like this:
<a href="http://martin.atkins.me.uk/" class="url" rel="me">
or, like this:
<a href="http://martin.atkins.me.uk/" class="url uid">
or have I missed something?
Stephen Paul Weber
Hash: SHA1
> then I would presumably need to have a link within my hCard like this:
> <a href="http://martin.atkins.me.uk/" class="url" rel="me">
>
> or, like this:
> <a href="http://martin.atkins.me.uk/" class="url uid">
>
You could also have:
<a href="http://twitter.com/you" class="url" rel="me">me on twitter</a>
- --
Stephen Paul Weber, @singpolyma
Please see <http://singpolyma.net> for how I prefer to be contacted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJSXAa6oSxepE9BOsRAqmjAKC4Gemboyc2x9c9VkaU7R9BIcJaYACgkT09
gcSfvDD585x0sYWk0wkobI4=
=+u2s
-----END PGP SIGNATURE-----
Stephen Paul Weber
Hash: SHA1
> I can always count on you for the hcard pimpage, Stephen. ;)
:)
> My pushback is that I had my avatar on factoryjoe.com in a hidden DIV. It
> added 50K to essentially a 30K document and made it load slowly on mobile
> devices. Hard to say whether that extra weight was worth it compared with
> linking it in the head of the document.
>
> Otherwise, I would agree that hcard is a great solution when the avatar is
> intended to be visible on the page.
Certainly. Microformats can be used for hidden data, but are less useful
for that in general.
However, most "profile pages" have a photo on them, or at least a link
to a page that has a photo of them (yes, rel=me spidering is expensive,
that's why I power the avatars on my contacts page with socialsearchme...
also, it's not too expensive if you only crawl to one level).
> Still, passing this data either as an encoded value or as a URL via PoCo,
> SREG or AX would seem to be a good idea, if only to increase the likelihood
> of adoption.
Sure, sreg is nice if only because it's really easy to implement. No
reason why providers couldn't start supporting sreg.photo today, and
some libraries may not even need to be modified to support it :)
> Let me put it this way: let's advocate for people support SOME mechanism for
> identifying the avatar for a given URL -- hcard, <link>, SREG or otherwise?
Certainly. Supporting 6 schemes is better than 0. And better than
gravatar.
- --
Stephen Paul Weber, @singpolyma
Please see <http://singpolyma.net> for how I prefer to be contacted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJSXFE6oSxepE9BOsRAjPXAJsEMDQ2VDSsQ92YJM+UeAKffG8DWgCfRish
sbUTpd5aBifbzk3RKvAXwBQ=
=SdKn
-----END PGP SIGNATURE-----