W3C home > Mailing lists > Public > public-fedsocweb@w3.org > November 2012

Re: avatar.js

From: Nick Jennings <nick@silverbucket.net>
Date: Thu, 22 Nov 2012 15:53:57 +0100
Message-ID: <CAJL4WtaKzRhPcx+USaNDOawBYusoV_jAo6uxh1Ug=b7BBbHpnA@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: webfinger@googlegroups.com, Dan Brickley <danbri@danbri.org>, Joseph Smarr <jsmarr@gmail.com>, public-fedsocweb@w3.org
On Thu, Nov 22, 2012 at 3:42 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> On 22 November 2012 15:34, Brad Fitzpatrick <bradfitz@google.com> wrote:
>> On Nov 22, 2012 6:31 AM, "Melvin Carvalho" <melvincarvalho@gmail.com>
>> wrote:
>> > On 22 November 2012 15:18, Brad Fitzpatrick <bradfitz@google.com> wrote:
>> >>
>> >> My native name in my preferred script or my Romanized name?
>> >
>> > Lots of existing work in this area in the last decade or more
>> >
>> > FOAF, VCard, Portable Contacts, OpenSocial, W3C PIM, Schema.org, Open
>> > Graph Protocol, to name just a few
>> >
>> > I would hope it were possible to reuse some of the link relations in the
>> > XRD?
>>
>> Exactly. Let's not ignore that work and clone it poorly.

I don't really think it's cloning the work of the area of 'contact
details' just to have a full name of the person. For example, a
WebFinger request is made and collects all the links associated with
that user (avatar, vcard, blog) ... before you download and import
their vcard, you probably want a little bit of clarity that this is
the person you are looking for. You already entered the email address,
but a confirmation on the name would be something that I think is
pretty reasonable.

...
Nick Jennings
nick@silverbucket.net
[link to vcard]
[link to blog]
...

So providing a relation entry for 'full name' of some sort, provides
the developer a way to easily display the basic (very basic) details
to the end-user without having to make a second HTTP call to first
download the vcard (which could be hosted on another domain that may
not provide CORS headers) and parse it just to extract the name.

Just a thought though, I'm open to other options I just don't like the
idea of having to make a second call.
-Nick




>
> We had a few telecons about this back when this group was the social web
> incubator group.
>
> It was loosely agreed, that things would try and converge around the
> portable contacts and vcard schemas.  But this was 2-3 years ago.  It partly
> depends ability to spend time keeping terms up to date.
>
> Jo Smarr and Dan Brickley (both at Google, I believe) are probably the best
> experts I know in this area.
>
> I've cc'd them both in case they are interested in this, perhaps also, if
> either gets some time free, it may be possible work out which vocabularies
> to reuse.
>>
>> >
>> >>
>> >> Etc.
>> >>
>> >> Fine to add some of these things but we (here, now) don't necessarily
>> >> have to, especially if it leads to distraction from shipping something
>> >> flexible.
>> >>
>> >> On Nov 22, 2012 6:14 AM, "Paul E. Jones" <paulej@packetizer.com> wrote:
>> >>>
>> >>> Many of the types in the current spec are just examples and not
>> >>> defined, yet. The webfinger.net ones are used today by people.
>> >>>
>> >>> I'm not sure why nobody defined a name field. Perhaps they thought it
>> >>> was enough to just grab the vcard? A name field with the person's preferred
>> >>> name and in the right order would be useful, I think.
>> >>>
>> >>> Paul
>> >>>
>> >>> ________________________________
>> >>> From: Nick Jennings <nick@silverbucket.net>
>> >>> Sent: Thu Nov 22 04:19:13 EST 2012
>> >>> To: "Paul E. Jones" <paulej@packetizer.com>
>> >>> Cc: webfinger@googlegroups.com, public-fedsocweb@w3.org
>> >>> Subject: Re: avatar.js
>> >>>
>> >>> Hi Paul,
>> >>>
>> >>> On Thu, Nov 22, 2012 at 2:00 AM, Paul E. Jones <paulej@packetizer.com>
>> >>> wrote:
>> >>>
>> >>>
>> >>>> Very cool!
>> >>>>
>> >>>> I’d like to see a whole profile page built when a user ID is entered,
>> >>>> but
>> >>>> this is definitely a good start that demonstrates that it’s working!
>> >>>
>> >>>
>> >>>
>> >>> Yes, I plan to extend the library to add this information, one thing I
>> >>> thought was odd is, why do we have entries for avatar, blog, etc. but
>> >>> not an entry for 'full name'?
>> >>>
>> >>>
>> >>>>
>> >>>>
>> >>>> From: webfinger@googlegroups.com [mailto:webfinger@googlegroups.com]
>> >>>> On
>> >>>> Behalf Of Melvin Carvalho
>> >>>>
>> >>>>
>> >>>> Sent: Wednesday, November 21, 2012 8:34 AM!
>> >>>>
>> >>>> To: Nick Jennings
>> >>>> Cc: public-fedsocweb@w3.org; webfinger@googlegroups.com
>> >>>> Subject: Re: avatar.js
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> On 21 November 2012 11:25, Nick Jennings <nick@silverbucket.net>
>> >>>> wrote:
>> >>>>
>> >>>> Hello All,
>> >>>>
>> >>>>
>> >>>>
>> >>>> This is my first time posting to both the fedsocweb and webfinger
>> >>>> lists. My
>> >>>>
>> >>>>
>> >>>> name is Nick Jennings and I'm a long-time open-source hacker, though
>> >>>> until
>> >>>> recently I haven't been very active in the problem domain of the open
>> >>>> social
>> >>>> web. Michiel de Jong and I have been working on a simple avatar.js
>> >>>> library
>> >>>>
>> >>>>
>> >>>> which takes an email address, and uses WebFinger to query the host
>> >>>> portion
>> >>>> and return the avatar URL, if found.
>> >>>>
>> >>>>
>> >>>>
>> >>>> It currently uses the /.well-known/host-meta.json endpoint as it's
>> >>>> starting
>> >>>> default, then falls back to host-meta (if not found). Likewise with
>> >>>> HTTPS
>> >>>>
>> >>>>
>> >>>> falling back to HTTP. I see there is a WebFinger draft 3 in progress
>> >>>> which
>> >>>> will change the end!
>> >>>>  point to
>> >>>> /.well-known/webfinger, so I'll update that as
>> >>>> the default soon, with a fallback to host-meta*. Of course, the
>> >>>> server will
>> >>>> need to support CORS since this is a pure JavaScript browser client
>> >>>> library,
>> >>>> so it doesn't work with gmail.com email addresses.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> First of all great work!  The demo is simple and intuitive, it's
>> >>>> great you
>> >>>> can see the results right away.
>> >>>>
>> >>>> One thing that we do sometimes is fall back to a CORS proxy when the
>> >>>> remote
>> >>>> server does not offer CORS.  I'm surprised gmail does not.
>> >>>>
>> >>>>
>> >>>>
>> >>>> Any plans to support other identifiers that have an avatar such as
>> >>>> http?
>> >>>> Then you can get avatars from indieweb users, facebook, tent.io etc.
>> >>>> too ...
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> A demo can be found here:
>> >>>>
>> >>>> http://silverbucket.github.com/avatar.js/
>> >>>>
>> >>>>
>> >>>>
>> >>>> and the repository:
>> >>>>
>> >>>> !
>> >>>>  http://github.com/silverbucket/avatar.js
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> Feedback welcome!
>> >>>>
>> >>>> -Nick
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >
>
>
Received on Thursday, 22 November 2012 14:54:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 November 2012 14:54:58 GMT