Notices sent via the web can have locations attached (via W3C geolocation), and notices sent via the API can too (via some new API parameters). It seems that 2 other popular notice methods cannot provide location information: email/sms, and XMPP. Email can't really be fixed, so I won't worry about that - but XMPP can.
XEP-0080 provides a way for XMPP clients to broadcast location changes. However, the location data is completely seperated from the chat messages we use to create notices. So we cannot simply take the location from the message data like we do with API or the web. I was thinking that we could create a new, 3 column table: jid, updated, location. When our XMPP bot receives a location update, it writes to the table. When an XMPP message is message sent to the bot to create a notice, we read the table, look up the jid, and if the location data isn't too old (we'd need to figure out a reasonable max age), attach that location as the notice's location. How does this approach sound? Thanks, ~Craig _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
