On 12/14/09 8:09 AM, Evan Prodromou wrote:
Aldon Hynes wrote:
As a person who regularly microblogs from my desktop, my laptop and my
mobile device, I am a regular with the edge case that Craig described
as are
many of the people that I live microblog from at conferences.
I think Craig's approach makes a lot more sense.
Aldon, I think you're an exceptional person, but even you aren't ever in
two places at the same time.
The difficulty I think is that XEP-0080 specifies that location updates
are sent asynchronously in a pub-sub manner, so we have to save the
updates to attach the location to a future message that might come in
from the same client.
http://xmpp.org/extensions/xep-0080.html#transport
So if we consider this (I think not too off-the-wall) case:
* desktop computer stays logged in all the time at home/work
* laptop or phone roves around, sometimes logs in
While the human is only in one place at a time, he/she may easily have
two or more connections open and reporting their -- separate -- locations.
If the desktop was the last to send a location ping with "Hey! I'm in
San Francisco", I don't want that to override my laptop's having said
"Hey! I'm in Montreal" if I post from the laptop when traveling.
From what I understand, associating the last-reported location with the
complete jid (including resource, to distinguish between separate
connections) would indeed handle these cases nicely if we're only
interested in using the XMPP location info for XMPP-sourced messages.
I'm not sure we'd want to update the profile location unless we want to
carry the location updates over to notices sent from other communication
channels... personally I tend to think of profile fields as something I
fill out manually, with the 'location' or 'city' field referring to my
home base.
If we do want it to auto-update, we might want to present it
differently, more as a "last known location"... and have it also update
when sending notices if we get updated locations from the web interface
or API postings.
-- brion vibber (brion @ status.net)
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
