On Sat, Jul 17, 2010 at 2:39 AM, Peter Saint-Andre <stpe...@stpeter.im> wrote: > There's an inconsistency between last activity (XEP-0012) and various > other time-related specs (XEPs 82, 202, 203). Consider: > > <iq from='jul...@capulet.com' > id='last1' > to='ro...@montague.net/orchard' > type='result'> > <query xmlns='jabber:iq:last' seconds='903'/> > </iq> > > vs. > > <iq type='result' > from='jul...@capulet.com/balcony' > to='ro...@montague.net/orchard' > id='time_1'> > <time xmlns='urn:xmpp:time'> > <tzo>-06:00</tzo> > <utc>2006-12-19T17:58:35Z</utc> > </time> > </iq> > > <presence from='jul...@capulet.com/balcony' to='ro...@montague.net'> > <status>anon!</status> > <show>xa</show> > <priority>1</priority> > <delay xmlns='urn:xmpp:delay' > from='jul...@capulet.com/balcony' > stamp='2002-09-10T23:41:07Z'/> > </presence> > > We see this clearly in XEP-0256: > > <presence from='jul...@capulet.com/balcony' to='ro...@montague.net'> > <show>away</show> > <query xmlns='jabber:iq:last' seconds='600'/> > <delay xmlns='urn:xmpp:delay' > from='capulet.com' > stamp='2002-09-10T23:41:07Z'/> > </presence> > > I wonder if we want to add a UTC timestamp to XEP-0012... > > <iq from='jul...@capulet.com' > id='last1' > to='ro...@montague.net/orchard' > type='result'> > <query xmlns='jabber:iq:last' > seconds='903' > stamp='2002-09-10T23:41:07Z'/> > </iq> > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > > >
I'd love that. Not having a fixed timestamp was one reason last activity didn't make it into XEP-0227 (IIRC it was the only data servers commonly stored which didn't make it into the current version of the XEP). The relative-to-now time it currently uses is awkward in various ways. Servers internally store timestamps, not 'seconds', and I suspect clients convert 'seconds' to timestamps on receiving last activity. -- Waqas
