<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<body text="#000000" bgcolor="#ffffff">
<pre wrap="">> <evanp> Hey, Bob, I just changed my avatar. Check it out!
> <bobw> [click]
> <bobw> Cool!
> <evanp> Thanks!
Good one! hehe.. ;-P
Evan Prodromou wrote:<br>
<pre wrap="">"BW" == Bob Wyman <a class="moz-txt-link-rfc2396E" href="mailto:firstname.lastname@example.org"><email@example.com></a> writes:
BW> The use of PubSub overcomes what would, for many people, be a
BW> major objection to the approach that you propose. That is:
First off, I posit that this is _not_ actually a major objection from
the point of view of users. From the point of view of the computer
scientist developing the toaster, sure, there's a problem with not
having pushed avatars. There's also a problem with not having VRML
sound-enhanced 3D movie avatars, or shared avatar banks, or
multigeneration version control of avatar object patterns in
namespaced pipelined collection chunks.
Dead Simple Avatars are just that: dead simple. They're the 80%
solution, and they do pretty much what most people want out of
avatars: associate an image with a JID.
BW> Your approach requires polling of the vCard from time to time
BW> to determine whether or not the avatar has changed.
The DSA JEP I proposed has Implementation Notes that specifically
recommend _against_ polling. The user should be able to explicitly
request an update, say by clicking on the screen display of the
avatar. Simple and intuitive.
<evanp> Hey, Bob, I just changed my avatar. Check it out!
My experience with avatars in other IM systems is that they are in
fact _rarely_ changed. And my experience with questions about avatars
on this list is that people want a working solution now, not a year
from now. DSAs can be implemented today, by anyone.