tag:google.com,2010:buzz:z120ezfb3vy5wvqtj224yfkr1t2nwzjq404
Julian Bond
106416716945076707395
5 Jul 2010
5 Jul 2010
Mobile
Public
46-71 Trinity Rd, Ware
46-71 Trinity Rd, Ware, Hertfordshire SG12 7, UK
51.813964
-0.0258909
Julian Bond
106416716945076707395
5 Jul 2010
5 Jul 2010
Mobile
Public
Another location test as I try to float Buzz through to Twitter and retain the location data.
Another location test as I try to float Buzz through to Twitter and retain the location data.
Another location test as I try to float Buzz through to Twitter and retain the location data.
tag:google.com,2010:buzz-comment:z120ezfb3vy5wvqtj224yfkr1t2nwzjq404:1278344405827000
Rob Nelson
117171737258103261935
I'm really interested in that solution if you come up with it.
5 Jul 2010
5 Jul 2010
Rob Nelson
117171737258103261935
I'm really interested in that solution if you come up with it.
5 Jul 2010
5 Jul 2010
Permalink
tag:google.com,2010:buzz-comment:z120ezfb3vy5wvqtj224yfkr1t2nwzjq404:1278344685859000
Julian Bond
106416716945076707395
@Rob Nelson buzz2twitter, Twitterfeed, buzzcan tweet now trying Feedburner. None of them seem to do this. Meanwhile Twitter still hasn't released their code to set location in the desktop UI. And neither has Buzz, so I'm use m.google.com to post in desktop Chrome. Seem to have been trying to get all this stuff to play nicely with location data all year.
5 Jul 2010
5 Jul 2010
Julian Bond
106416716945076707395
@Rob Nelson buzz2twitter, Twitterfeed, buzzcan tweet now trying Feedburner. None of them seem to do this. Meanwhile Twitter still hasn't released their code to set location in the desktop UI. And neither has Buzz, so I'm use m.google.com to post in desktop Chrome. Seem to have been trying to get all this stuff to play nicely with location data all year.
5 Jul 2010
5 Jul 2010
tag:google.com,2010:buzz-comment:z120ezfb3vy5wvqtj224yfkr1t2nwzjq404:1278350377852000
Julian Bond
106416716945076707395
Oh well. Feedburner didn't pass through the location data either.
5 Jul 2010
5 Jul 2010
Julian Bond
106416716945076707395
Oh well. Feedburner didn't pass through the location data either.
5 Jul 2010
5 Jul 2010
tag:google.com,2010:buzz-comment:z120ezfb3vy5wvqtj224yfkr1t2nwzjq404:1278351768757000
Rob Nelson
117171737258103261935
Might be able to get that pulled out with a yahoo pipe
5 Jul 2010
5 Jul 2010
Rob Nelson
117171737258103261935
Might be able to get that pulled out with a yahoo pipe
5 Jul 2010
5 Jul 2010
tag:google.com,2010:buzz-comment:z120ezfb3vy5wvqtj224yfkr1t2nwzjq404:1278358932137000
Julian Bond
106416716945076707395
@Rob Nelson The location data is in the Buzz Atom feed. So whatever tool is used to read that and post into Twitter needs to be aware of the location extensions in the Twitter. As far as I can tell, none of them are yet. The problem is not getting location data out of Buzz or reformatting the RSS/Atom. The problem is posting into Twitter. There are support calls for things like Twitterfeed going back to last year asking for this. It's not hard.
What I should probably do is to write my own for my own use. I just don't want to host for others and have the responsibility for keeping it running. 5 Jul 2010 5 Jul 2010
Julian Bond
106416716945076707395
@Rob Nelson The location data is in the Buzz Atom feed. So whatever tool is used to read that and post into Twitter needs to be aware of the location extensions in the Twitter. As far as I can tell, none of them are yet. The problem is not getting location data out of Buzz or reformatting the RSS/Atom. The problem is posting into Twitter. There are support calls for things like Twitterfeed going back to last year asking for this. It's not hard.
What I should probably do is to write my own for my own use. I just don't want to host for others and have the responsibility for keeping it running. 5 Jul 2010 5 Jul 2010