Location support
Bug #484586 reported by
Craig
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Gwibber |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Starting with StatusNet 0.9, SN supports the Twitter location API. For example, as documented by Twitter at http://
It would be awesome if Gwibber could use the GPS to provide the lat/long with status updates (if the user permits that, of course). Perhaps GeoClue could be used at the location provider?
| Changed in gwibber: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
To post a comment you must log in.
Three backends support the same location API calls: Twitter, Qaiku and StatusNet.
* You can send a `lat` and `long` when posting a message via statuses/update
* All messages that are positioned carry a GeoRSS Point property (GeoRSS for XML, GeoJSON for JSON)
* Searches in at least Qaiku and Twitter can be limited to a geographical area via the `geocode` parameter