[twitter-dev] /statuses/destroy error erroneously?
Calling /statuses/destroy (on a valid status ID) seems to return a 400 error with a "Bad request. We could not delete that status for some reason.." ... but the status is successfully deleted. Bug?
[twitter-dev] Re: Developer Preview: Geolocation API
Hi Damon. Yup - we've started updating the docs. Generally, there will always be a in the (it may just be empty, however, if there is no geolocated information attached), and there will always be a on every which is a boolean representing whether the user has enabled geolocation on his or her account. On Aug 21, 2009, at 6:46 PM, Damon Clinkscales wrote: On Aug 20, 3:46 pm, Ryan Sarver wrote: We wanted to give you all a heads up on a cool new feature that is coming soon - Geolocation. We have also updated the wiki to reflect what the API will look like when it launches, so check it out and let us know if you have any questions:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A- statuses%C2%A0u...http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve ... Ryan, Very cool stuff. Looking forward to it. I'm assuming that you'll update the wiki (and API when it launches) such that everywhere a element is returned, it will contain a element? Thanks, -damon
[twitter-dev] Stop playing around with Source parameters
Recently you added nofollow's, and now you moved the nofollow after the href. Some of us filter these out and you changing them is only making it more complicated. Please make up your mind and stop changing these... http://fun140.com/";>Fun140 http://fun140.com/";>Fun140 http://fun140.com/"; rel="nofollow">Fun140
[twitter-dev] Re: Developer Preview: Geolocation API
wonder what the API would return for my current location :) http://deancollinsblog.blogspot.com/2009/08/gogo-internet.html From: twitter-development-talk@googlegroups.com on behalf of Damon Clinkscales Sent: Fri 8/21/2009 9:46 PM To: Twitter Development Talk Subject: [twitter-dev] Re: Developer Preview: Geolocation API On Aug 20, 3:46 pm, Ryan Sarver wrote: > We wanted to give you all a heads up on a cool new feature that is coming > soon - Geolocation. > We have also updated the wiki to reflect what the API will look like when it > launches, so check it out and let us know if you have any > questions:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u...http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve... > Ryan, Very cool stuff. Looking forward to it. I'm assuming that you'll update the wiki (and API when it launches) such that everywhere a element is returned, it will contain a element? Thanks, -damon <>
[twitter-dev] Re: how can I get user address using Twitter API?
Is there any reason twitter doesn't support it? it is so weird. On Aug 21, 6:03 am, JDG wrote: > no, on purpose. > > On Fri, Aug 21, 2009 at 01:08, Bo Huang wrote: > > > Hi, > > > I am trying to integrate Twitter OAuth with my website. Right now I > > can use this API (https://twitter.com/account/verify_credentials.xml) > > to get lots of profile information like user ID, screen name, but I > > didn't any info about the user email address. Is there any API to get > > email address? Thanks in advance. > > > Bo > > -- > Internets. Serious business.
[twitter-dev] Re: Developer Preview: Geolocation API
On Aug 20, 3:46 pm, Ryan Sarver wrote: > We wanted to give you all a heads up on a cool new feature that is coming > soon - Geolocation. > We have also updated the wiki to reflect what the API will look like when it > launches, so check it out and let us know if you have any > questions:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u...http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve... > Ryan, Very cool stuff. Looking forward to it. I'm assuming that you'll update the wiki (and API when it launches) such that everywhere a element is returned, it will contain a element? Thanks, -damon
[twitter-dev] Re: API profile image update
Hi.
I finally managed to get my image update code working, too. In case
someone still has problems here are my findings / observations:
* There only must be one blank line between HTTP request header and
body (java jersey created two).
* Newlines in request header and multipart headers must be CR/LF (both
characters).
* It is NOT important that the following headers exist - you CAN skip
them: User-Agent, Content-Length. Expect
* The blank before "boundary" in "Content-Type: multipart/form-data;
boundary=..." is NOT important.
* But it IS important that you mention the boundary in the content
type header (jersey skipped it).
* Each part of the multipart content begins with "--" + boundary
* The end of the last part is marked with "--" + boundary + "--"
* It is important that the header of the file part also contains a
filename.
Taken together the working request looks like this
("working" of course only after you have to inserted real
authentication and binary data).
POST https://twitter.com/account/update_profile_background_image.xml
Authorization: Basic your_auth_string
Content-Type: multipart/form-data; boundary=some_unique_string
--some_unique_string
Content-Disposition: form-data; name="image"; filename="image.gif"
Content-Type: image/gif
your binary data goes here
--some_unique_string
Content-Disposition: form-data; name="tile"
Content-Type: text/plain
true
--some_unique_string--
Thanks to josh (he sent me his findings via private mail).
Thanks to David, too (he wrote about the problem with two blank lines
between header and body in
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4fe78c5c7fb5cbdf/59f9ef7c8f745f93
Mitchel
[twitter-dev] Re: Developer Preview: Geolocation API
Will this apply to direct messages too? On Aug 21, 12:44 pm, Ryan Sarver wrote: > Ben, > > Currently we geocode your user.location data to get an idea of where > you are. That gets attached to each tweet as it comes in, but its not > usually a representation of where you were when you actually sent the > tweet. The new functionality will allow you to geotag the actual > update without modifying the user.location field. > > When it comes to search, we'll use both and give priority to the > tweet-level geotag. > > Make sense? > > Best, Ryan > > On Fri, Aug 21, 2009 at 4:06 AM, Ben Eliott > wrote: > > Hi, > > Please could you advise on the differences between this and the current > > location based searching facility? Is the current location search based on > > the users location in their settings whilst this is a exact location for > > each tweet? > > Thanks, > > Ben > > On 20 Aug 2009, at 21:46, Ryan Sarver wrote: > > > We wanted to give you all a heads up on a cool new feature that is coming > > soon - Geolocation. The Geolocation API will give us the ability to attach > > geographic metadata to tweets to provide additional context with your > > update. Along with the option to tag updates, we will be able to search for > > nearby tweets and view the geo metadata in user timelines. The additional > > context allows for us to deliver more meaningful and localized experiences > > to users. We are also really excited about a unique facet of this release in > > that it will be API-only initially. This means that Twitter.com won't > > surface the functionality and we look forward to seeing the new and > > interesting experiences that will grow out of the ecosystem. > > > As part of our Geolocation efforts we will soon be publishing "Geolocation > > Best Pracitices" to guide everyone through issues like security and privacy > > as well as discussing some ideal experiences for users. Topics will include > > things like storage of location data, what to do with a user's historical > > data, how to present the concept of geotagging and more. The guide will > > create a framework from which we can address the challenges that come about > > when dealing with something as sensitive as someone's location while > > hopefully allowing everyone enough creative freedom to create their own > > experiences around it. > > It > > is important to note that the feature is going to be strictly opt-in. It will be disabled until a user chooses to switch it on. We will provide a read-only attribute > > on the user object so an app can detect if the user has it > > disabled and let them know if they need to turn it on before using a > > geolocation feature. > > > While we can't provide an exact date for launch, you should plan on having a > > few weeks of development time before the new API is officially launched. > > With that being said, lets get to it... > > > Example: Geotagging a Tweet > > --- > > curl -d "lat=37.780467&long=-122.396762&status=I have arrived" -u user:pass > > "http://twitter.com/statuses/update.xml"; > > > > > > > > > Tue Apr 07 22:52:51 + 2009 > > > ... > > > http://www.georss.org/georss";> > > > 37.780467 -122.396762 > > > > > > > > > 1401881 > > > Doug Williams > > > ... > > > true > > > ... > > > > > > > > > We have also updated the wiki to reflect what the API will look like when it > > launches, so check it out and let us know if you have any questions: > >http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u... > >http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve... > > We'll also be in our recently announced IRC channel (#twitterapi > > on irc.freenode.net) if you want to discuss the announcement with the team. > > > Ryan > > PM, Platform Team > >http://twitter.com/rsarver
[twitter-dev] Re: DM Length
On Thu, Aug 20, 2009 at 9:44 AM, Dewald Pretorius wrote: > > There is something very quirky going on with DMs. That 841-character > DM that I received is now only returning 247 characters when I > retrieve it via the API. ~245 character (bytes?) DMs have been working for some time now, through API methods. I assume this is a temporary situation, but it is kind of handy :-) TjL
[twitter-dev] statuses/followers stops returning results after page 101
Trying to quickly get follower information (screen name, bio, etc). Using statuses/followers but after page 101 it no longer returns results. I believe this used to go far past page 101 in the past. I don't believe the docs say that there is a limitation on pages.. is this a bug?
[twitter-dev] Track API Limit message meaning
Hi guys,
I am currently testing a library for using the track API in order to
make sure that I'm following all the rules exposed on the docs. While
running against the real API I have noticed sporadic messages in the
form:
{"limit":{"track":121564}}
According to the docs:
[q]Track streams may also contain limitation notices, where the
integer track is an enumeration of statuses that matched the track
predicate but were administratively limited. [/q]
I am not very sure that I'm correctly interpreting the above text as:
1. the "track" value seems to always be a single value
2. the "track" value seems to be growing in time
3. the "track" value doesn't seem to be a twitter message id
Could you please clarify a bit the meaning of these messages?
Many thanks in advance,
./alex
PS: I've asked John (@jkalucki) about this and while I've got an
answer from him (thanks a bunch John), I'm still not sure I'm getting
it.
[twitter-dev] Re: heavy throttling by search.twitter.com API from GAE application
Hello, I have replied to Jud off-list, but for everyone's benefit we'd like to reiterate that AWS and GAE are shared resources and therefore share the rate limit across applications. A dedicated IP and unique UA will guarantee the maximum API limits. There are several cheap and reliable VPS hosting services available which can provide a dedicated IP address and full control over the server. Thanks, -Chad On Fri, Aug 21, 2009 at 12:48 PM, Jud wrote: > > I've got a python app running on Google App Engine (appspot hosted) > that queries http://search.twitter.com/search.atom?q= for simple > queries (e.g. "foo OR bar"), and it's being severely throttled (e.g. > can't get a successful request through (response 200 w/ data) more > than a couple of times per _hour_). > > - I'm setting the UA string to something unique/identifiable (e.g. my > company name) > - I'm respecting the retry-after header coming back when I see a 503 > (average retry-after duration is ~750) > - GAE turns the IP address behind the app over ~ every 6 hours > - app hits tries to hit search.twitter.com every 5 minutes. > > I've successfully polled the endpoint at much higher rates (in > completely different IP address ranges) in the past, without issue. > Unclear what's going on. Any suggestions would be greatly appreciated.
[twitter-dev] Re: heavy throttling by search.twitter.com API from GAE application
I agree GAE throttle on the Search API is not behaving as it has in the past, Can someone please look into this? -Ben Hedrington On Aug 21, 11:48 am, Jud wrote: > I've got a python app running on Google App Engine (appspot hosted) > that querieshttp://search.twitter.com/search.atom?q=for simple > queries (e.g. "foo OR bar"), and it's being severely throttled (e.g. > can't get a successful request through (response 200 w/ data) more > than a couple of times per _hour_). > > - I'm setting the UA string to something unique/identifiable (e.g. my > company name) > - I'm respecting the retry-after header coming back when I see a 503 > (average retry-after duration is ~750) > - GAE turns the IP address behind the app over ~ every 6 hours > - app hits tries to hit search.twitter.com every 5 minutes. > > I've successfully polled the endpoint at much higher rates (in > completely different IP address ranges) in the past, without issue. > Unclear what's going on. Any suggestions would be greatly appreciated.
[twitter-dev] heavy throttling by search.twitter.com API from GAE application
I've got a python app running on Google App Engine (appspot hosted) that queries http://search.twitter.com/search.atom?q= for simple queries (e.g. "foo OR bar"), and it's being severely throttled (e.g. can't get a successful request through (response 200 w/ data) more than a couple of times per _hour_). - I'm setting the UA string to something unique/identifiable (e.g. my company name) - I'm respecting the retry-after header coming back when I see a 503 (average retry-after duration is ~750) - GAE turns the IP address behind the app over ~ every 6 hours - app hits tries to hit search.twitter.com every 5 minutes. I've successfully polled the endpoint at much higher rates (in completely different IP address ranges) in the past, without issue. Unclear what's going on. Any suggestions would be greatly appreciated.
[twitter-dev] Re: Developer Preview: Geolocation API
Ben, Currently we geocode your user.location data to get an idea of where you are. That gets attached to each tweet as it comes in, but its not usually a representation of where you were when you actually sent the tweet. The new functionality will allow you to geotag the actual update without modifying the user.location field. When it comes to search, we'll use both and give priority to the tweet-level geotag. Make sense? Best, Ryan On Fri, Aug 21, 2009 at 4:06 AM, Ben Eliott wrote: > Hi, > Please could you advise on the differences between this and the current > location based searching facility? Is the current location search based on > the users location in their settings whilst this is a exact location for > each tweet? > Thanks, > Ben > On 20 Aug 2009, at 21:46, Ryan Sarver wrote: > > We wanted to give you all a heads up on a cool new feature that is coming > soon - Geolocation. The Geolocation API will give us the ability to attach > geographic metadata to tweets to provide additional context with your > update. Along with the option to tag updates, we will be able to search for > nearby tweets and view the geo metadata in user timelines. The additional > context allows for us to deliver more meaningful and localized experiences > to users. We are also really excited about a unique facet of this release in > that it will be API-only initially. This means that Twitter.com won't > surface the functionality and we look forward to seeing the new and > interesting experiences that will grow out of the ecosystem. > > As part of our Geolocation efforts we will soon be publishing "Geolocation > Best Pracitices" to guide everyone through issues like security and privacy > as well as discussing some ideal experiences for users. Topics will include > things like storage of location data, what to do with a user's historical > data, how to present the concept of geotagging and more. The guide will > create a framework from which we can address the challenges that come about > when dealing with something as sensitive as someone's location while > hopefully allowing everyone enough creative freedom to create their own > experiences around it. > It > is important to note that the feature is going to be strictly opt-in. It will be disabled until a user chooses to switch it on. We will provide a read-only attribute > on the user object so an app can detect if the user has it > disabled and let them know if they need to turn it on before using a > geolocation feature. > > While we can't provide an exact date for launch, you should plan on having a > few weeks of development time before the new API is officially launched. > With that being said, lets get to it... > > Example: Geotagging a Tweet > --- > curl -d "lat=37.780467&long=-122.396762&status=I have arrived" -u user:pass > "http://twitter.com/statuses/update.xml"; > > > > > > Tue Apr 07 22:52:51 + 2009 > > ... > > http://www.georss.org/georss";> > > 37.780467 -122.396762 > > > > > > 1401881 > > Doug Williams > > ... > > true > > ... > > > > > > We have also updated the wiki to reflect what the API will look like when it > launches, so check it out and let us know if you have any questions: > http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update > http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials > We'll also be in our recently announced IRC channel (#twitterapi > on irc.freenode.net) if you want to discuss the announcement with the team. > > Ryan > PM, Platform Team > http://twitter.com/rsarver >
[twitter-dev] Re: Developer Preview: Geolocation API
On Aug 21, 11:39 am, Cameron Kaiser wrote: > Even so, though, I don't think that would fully get around the malicious > application problem unless you could say *which* apps got to turn it on and > off, and even then ... True. I guess the scenario I'm thinking of is: you've opted in, 99% of the time you are fine with publishing your location, but this one time you want to hide where you are tweeting from. The only option (for now) would be to log onto twitter.com and opt-out again. At a minimum, twitter needs to make the optin/optout work through m.twitter.com. As long as I'm throwing ideas out: - What if I could tell twitter to tag my tweets with my Google Latitude or Yahoo! FireEagle location? - What if I could tell twitter how granular I want my location to be (ie, even if my client publishes 40.96299,-72.13913, twitter only stores 40.96,-72.13) -- -ed costello
[twitter-dev] Re: Developer Preview: Geolocation API
Sean, We hope that user.location goes back to being more static and descriptive to where you are typically "based". In my case it will be "SOMA, San Francisco, CA". It will provide us additional context and be more informative to someone viewing your profile than "iPhone (42.1234, -1221234)". Nothing will really change about the way it works, but we expect the behavior to change a bit. Best, Ryan On Fri, Aug 21, 2009 at 1:54 AM, Sean Callahan wrote: > > Quick question Ryan, because none of this will surface on Twitter.com > will you keep the Location field for a users profile or is that going > away when this becomes love? If it stays, will there be any specific > changes regarding the location on a user's profile when this API > becomes available? > > Sean > > On Aug 20, 5:28 pm, Lepton wrote: >> Perfect timing! My iPhone app about to be released has a lot to do >> with geolocation, and already uses Twitter to set and see locations of >> people. Myallo HotList tracks the "hotness" of people and places in >> your social universe partly through their locations. For example as a >> person gets nearer to you, they get hotter, if friends gather near a >> place, they and the place get hotter. I want to use these upcoming >> features to "discover" nearby people. You can preview the app via its >> documentation athttp://myallo.com/hotlist >
[twitter-dev] Re: OAuth - get_request_token - 401 Unauthorized - ruby gem
Gonna chime in here with my obscure fix - check the system clock on the
production server?
On Fri, Aug 21, 2009 at 6:16 AM, srikanth reddy
wrote:
> This might help
>
> http://groups.google.com/group/twitter-development-talk/browse_frm/thread/13f5767d2d204a9d/607e14c5133e5726
>
>
> On Fri, Aug 21, 2009 at 4:12 PM, themire wrote:
>
>>
>> Hi,
>>
>> I've recently started to get 401 Unauthorized errors from twitter
>> while trying to get a request token.
>>
>> I'm using the OAuth Ruby gem and making the request from irb as
>> follows:
>>
>> OAuth::Consumer.new(our_secret, our_key,{ :site=>"http://
>> twitter.com" }).get_request_token()
>>
>> I've made the request from several different machines and got a good
>> request token back from twitter, but it seems to be giving the 401
>> errors only on our production server. This used to work fine on this
>> machine until recently.
>>
>> Is there still currently ongoing problems with the twitter api in this
>> regard?
>>
>> Thanks,
>> Julian
>>
>
>
[twitter-dev] Re: New problem with JSON search API on 32-bit OS?
we've seen this before on this list, and the suggestion i came up with is to manually parse the JSON for integer values (wouldn't be that hard) and wrap them in strings. On Fri, Aug 21, 2009 at 08:58, JSJ wrote: > > I have not seen this issue discussed anywhere yet. > > Recently my twitter search API code stopped working properly (using > search.json). After tracking down the issue here is what I think is > going on: > > - Recently, the status/message IDs returned by the search API began > exceeding the maximum positive integer allowed on 32-bit OS platforms > (2,147,483,647). For example, in a recent API call I am getting > message IDs such as 3,448,308,315. > - The twitter API returns these within the JSON string using integer > encoding. From PHP, when I decode the return JSON string using > json_decode on 32-bit Windows, I end up with ID values such as > -958,581,221 rather than 3,xxx,xxx,xxx. > - This causes a problem for both message IDs and the max_id parameter > which is required to get further pages of results. > - At the moment I cannot find a way to get the proper ID out of the > JSON payload without manually changing the raw JSON encoded string I > get back from twitter to force the IDs to be encoded as strings rather > than integers. This involves several search and replace operations and > thus is very inefficient. > - One alternative may be to switch to ATOM but I hoping to avoid that > as JSON is compact and works well. > - Ideally the JSON API could return the IDs using a string rather than > integer encoding > > Has anyone seen this and does anyone else have any ideas on how to > work around it? > > > -- Internets. Serious business.
[twitter-dev] Re: Developer Preview: Geolocation API
> > Users will need to come to the website to change the setting. If we > > provided an API, a misbehaving application would change the setting > > without the user knowing - hence the read-only attribute. > > Perfect, that_s what I_d expect. But I throw this out anyway: once > someone has opted in, would you consider adding an API method to allow > geo to be turned on/off? Or would you expect the individual > applications to allow users to mask their location when posting a > tweet? Even so, though, I don't think that would fully get around the malicious application problem unless you could say *which* apps got to turn it on and off, and even then ... -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- /etc/motd: /earth is 98% full. please delete anyone you can. ---
[twitter-dev] Re: New problem with JSON search API on 32-bit OS?
> Recently my twitter search API code stopped working properly (using
> search.json). After tracking down the issue here is what I think is
> going on:
>
> - Recently, the status/message IDs returned by the search API began
> exceeding the maximum positive integer allowed on 32-bit OS platforms
> (2,147,483,647). For example, in a recent API call I am getting
> message IDs such as 3,448,308,315.
> - The twitter API returns these within the JSON string using integer
> encoding. From PHP, when I decode the return JSON string using
> json_decode on 32-bit Windows, I end up with ID values such as
> -958,581,221 rather than 3,xxx,xxx,xxx.
I think this is PHP's problem. Perl doesn't have it; it sees this tweet
as ID 3 451 486 259, not a negative one relative to 2 147 483 647, and this
is on a very old Perl to boot. This is the actual dump from TTYtter's
internal hash:
[{'text','@mom2twinsplus1 you\'re welcome. alas, browser options are thin for
Mac OS 9, which is why we\'re working on
it.','to_user_id',276359,'to_user','mom2twinsplus1','from_user','doctorlinguist','id',3451486259,'from_user_id',2769,
As you can see, the ID is handled correctly.
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- If I am not for myself, who will be for me? -- Pirkei Avot -
[twitter-dev] Re: Developer Preview: Geolocation API
On Aug 20, 6:37 pm, Ryan Sarver wrote: > Users will need to come to the website to change the setting. If we > provided an API, a misbehaving application would change the setting > without the user knowing - hence the read-only attribute. Perfect, that’s what I’d expect. But I throw this out anyway: once someone has opted in, would you consider adding an API method to allow geo to be turned on/off? Or would you expect the individual applications to allow users to mask their location when posting a tweet? -- -ed costello
[twitter-dev] Following Protected Users
I'm writing a Twitter integration and am wondering how I would go about following users with "protected tweets". Whenever I attempt to follow one of these users (using the http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friendships%C2%A0create Friendship create method), I get a 403 response (our account is whitelisted, so it's not a rate limiting issue). Also, it doesn't seem that a "follow request" is being sent to these users. I've poured over the API and haven't found any explanation - is there possibly a different API method for requesting a follow for `protected` accounts? Thanks!
[twitter-dev] New problem with JSON search API on 32-bit OS?
I have not seen this issue discussed anywhere yet. Recently my twitter search API code stopped working properly (using search.json). After tracking down the issue here is what I think is going on: - Recently, the status/message IDs returned by the search API began exceeding the maximum positive integer allowed on 32-bit OS platforms (2,147,483,647). For example, in a recent API call I am getting message IDs such as 3,448,308,315. - The twitter API returns these within the JSON string using integer encoding. From PHP, when I decode the return JSON string using json_decode on 32-bit Windows, I end up with ID values such as -958,581,221 rather than 3,xxx,xxx,xxx. - This causes a problem for both message IDs and the max_id parameter which is required to get further pages of results. - At the moment I cannot find a way to get the proper ID out of the JSON payload without manually changing the raw JSON encoded string I get back from twitter to force the IDs to be encoded as strings rather than integers. This involves several search and replace operations and thus is very inefficient. - One alternative may be to switch to ATOM but I hoping to avoid that as JSON is compact and works well. - Ideally the JSON API could return the IDs using a string rather than integer encoding Has anyone seen this and does anyone else have any ideas on how to work around it?
[twitter-dev] Re: Developer Preview: Geolocation API
I think that issue can be simplified down to zip code radiAl query (simple) once you know the users relevent vicinity. It's not like browsers are actually accurate as an actual gps (netbooks iPhone... Chipsets will change that soon) Anyway just throwing in here... Scaryish topic (one I play with). What if you are celebrity + hit threat and your loc coordinates are available no matter what (oh yeah ggnkbghk!!! :)?) what do you do then? Anyway I won't post generic discussion further in this list I just started using or actually, I mean, SENDING to any lustserv (this and cake) If I am wrong on etiquette, I apologize --- will ttyl. :) I'm working on a few Twitter rhings myself. I own StockAPI.com. I imagine it might play and offer with others ;-)!!! Thanks, Matt Kaufman 917 512 6281 On Aug 21, 2009, at 10:36 AM, Mike Champion wrote: > > Very cool! > > Will Twitter Search be changed to use the new geo-tweet info? Right > now if you search for "near=Boston,MA" it seems to be mostly (only?) > looking at a user's location field. I'd be curious to know if Twitter > Search will be the best place to determine tweets within a given area > and how Search will behave if my "location" is set to Boston, but my > tweet georss is in SF, for example. > > Thanks, > > -mike > > On Aug 21, 9:59 am, "@epc" wrote: >> On Aug 20, 6:37 pm, Ryan Sarver wrote: >> >>> Users will need to come to the website to change the setting. If we >>> provided an API, a misbehaving application would change the setting >>> without the user knowing - hence the read-only attribute. >> >> Perfect, that’s what I’d expect. But I throw this out anyway: o >> nce >> someone has opted in, would you consider adding an API method to >> allow >> geo to be turned on/off? Or would you expect the individual >> applications to allow users to mask their location when posting a >> tweet? >> -- >> -ed costello
[twitter-dev] Re: Platform Status Update, Tuesday 2:00pm PST
Its been more than 2 days . The problem is not only with API. I tried deleting a tweet from web but all i could see is a flashing dot . It is not removing the entry. If i refresh manually then the tweet gets deleted. Srikanth On Fri, Aug 21, 2009 at 2:10 PM, lepah wrote: > > Hi, I'm having the same issue form my iphone twitter app, I'm deleting > status via http://www.twitter.com/statuses/destroy/id.xml and I'm > always getting a status 400 error which my app displays to the user > even though the status was deleted. > > is this a permanent change to the API?? > > thanks, > Matt > > On Aug 19, 4:49 pm, deepikagupta wrote: > > Hi, > > > > I am facing problem while Deleting any Tweet from my application. > http://www.twitter.com/statuses/destroy/id.xmlalways gives me400 > > status code but also deletes the tweet. So in my application it is > > caught as an exception only and error message is shown to user even > > though tweet is deleted. > > I am facing this issue only while deleting tweets and mentions. HTTP > > request for delete seems to be working fine with direct messages and > > favorites. > > > > Please Help me!!! > > > > On Aug 19, 8:46 am, djc8080 wrote: > > > > > > > > > Oops. spoke too soon. Still eradic problems - same symptoms. Incorrect > > > rate_limit response on statuses/followers when ..ids calls work > > > perfectly on the same account. >
[twitter-dev] Re: Developer Preview: Geolocation API
Hi Sean. The location field on the user's profile will be stating put! On Aug 21, 2009, at 1:54 AM, Sean Callahan wrote: Quick question Ryan, because none of this will surface on Twitter.com will you keep the Location field for a users profile or is that going away when this becomes love? If it stays, will there be any specific changes regarding the location on a user's profile when this API becomes available? Sean On Aug 20, 5:28 pm, Lepton wrote: Perfect timing! My iPhone app about to be released has a lot to do with geolocation, and already uses Twitter to set and see locations of people. Myallo HotList tracks the "hotness" of people and places in your social universe partly through their locations. For example as a person gets nearer to you, they get hotter, if friends gather near a place, they and the place get hotter. I want to use these upcoming features to "discover" nearby people. You can preview the app via its documentation athttp://myallo.com/hotlist
[twitter-dev] Re: Developer Preview: Geolocation API
Very cool! Will Twitter Search be changed to use the new geo-tweet info? Right now if you search for "near=Boston,MA" it seems to be mostly (only?) looking at a user's location field. I'd be curious to know if Twitter Search will be the best place to determine tweets within a given area and how Search will behave if my "location" is set to Boston, but my tweet georss is in SF, for example. Thanks, -mike On Aug 21, 9:59 am, "@epc" wrote: > On Aug 20, 6:37 pm, Ryan Sarver wrote: > > > Users will need to come to the website to change the setting. If we > > provided an API, a misbehaving application would change the setting > > without the user knowing - hence the read-only attribute. > > Perfect, that’s what I’d expect. But I throw this out anyway: once > someone has opted in, would you consider adding an API method to allow > geo to be turned on/off? Or would you expect the individual > applications to allow users to mask their location when posting a > tweet? > -- > -ed costello
[twitter-dev] Re: OAuth - get_request_token - 401 Unauthorized - ruby gem
This might help
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/13f5767d2d204a9d/607e14c5133e5726
On Fri, Aug 21, 2009 at 4:12 PM, themire wrote:
>
> Hi,
>
> I've recently started to get 401 Unauthorized errors from twitter
> while trying to get a request token.
>
> I'm using the OAuth Ruby gem and making the request from irb as
> follows:
>
> OAuth::Consumer.new(our_secret, our_key,{ :site=>"http://
> twitter.com" }).get_request_token()
>
> I've made the request from several different machines and got a good
> request token back from twitter, but it seems to be giving the 401
> errors only on our production server. This used to work fine on this
> machine until recently.
>
> Is there still currently ongoing problems with the twitter api in this
> regard?
>
> Thanks,
> Julian
>
[twitter-dev] Tees
I have a website (Scottigotit.com) i have great twitter phrases for customized tee shirts that i want to advertise on my site.Do i need to get approval from twitter, or do i have the green light for promoting twitter? Scottigotit
[twitter-dev] Need help with OAuth + update_profile_background_image
Hey all, I'm trying to change background image on the fly using an OAuth application, but running into some strange problems. Firstly, I should add that I can perform other requests (such as tweets and follows) without issue. I'm using abraham's twitterOAuth library. 1. When trying to post an image, in what format do I need the image? I'm not using a form to upload the image, but rather using PHP code to grab it remotely using fsockopen(). This seems to grab the raw image data, so I assume I'm doing things right up to this point. 2. My base_string seems to have the proper 3 parts, as follows: print_r($parts): array ( [0] => POST [1] => https://twitter.com/account/update_profile_background_image.xml [2] => image=GIF89a%5E%01%07%01%F7etc etc ) However, when the script implodes the three parts using an ampersand as the glue string, my variable name 'image' seems to be morphed into some strange ASCII character. To be exact, the imploded string should be "...background_image.xml&image%3D" but it is instead turned into "...background_image.xmlℑ%3D..." It appears to be morphed into the entity on this page (http:// htmlhelp.com/reference/html40/entities/symbols.html), but I have no idea how to work around that, since it seems to be done automatically in PHP. 3. Even after I work around that issue, I'm receiving an Incorrect Signature error on the entire image change request. Are there any other things that need to be fixed for image uploads to work properly? Thanks in advance, I can provide code or other details upon request!
[twitter-dev] Re: large user base push notification solutions?
When I developed Twe2, here are some of the things I have learnt - 2 minute delay is pretty short - users don't even notice it that much - at one point on Twe2 we changed it to a 15 minute delay an no one really complained. If users are getting pushed notifications they are normally away from a main terminal and thus are not watching twitter through TweetDeck; in short you don't need realtime to be that realtime - Also 99.99% of people don't get that many notifications a day, polling too often is a waste of time. - We supported about 40,000 users off 1 small VPS. - To get DM's you will need to use the users credentials (oauth or otherwise), a 2 minute interval means that you will use 30 of the users requests per hour (this might have changed) and as such they might get annoyed. - 500,000 users is pretty optimistic I wouldn't even worry about that scale just yet, just get your stuff working for now. - User since_id everywhere you can. - We launched with the ability to have quiet periods, that is no notifications while I am sleeping - people will thank you for this. Based on new developments of Twitter you can use something like follow, shadow and birddog - it offers a migration plan too, start with follow to get all the tweets from a user and to a user (200 users is good to test your API works), then when you launch request twitter to allow you to use shadow (50,000 users is a lot and will probably suit your app for a long time). Then as soon as you see a tweet on the stream you know it is for some of your users and you can fire it straight to them. the only issue is that these API's only get proper replies and not mentions. Currently none of the Streaming API's will help you for DM's (AFAIK). Paul Kinlan, http://www.Twollo.com 2009/8/21 ke...@nibirutech.com > > Hi > > I am a developer , trying to figure out a way to develop a push > notification solution for iPhone users. > > The easy way to do the push work, is to have a cron-job to check > users' new mentions and DMs. It should work for small number of > users. What if we have a large user base, say , 500, 000 users at > least? How can we use a proper solution to get a 2-minutes delay push > for any user's mentions and DMs? (we can't afford the server cost for > half million requests every 2 minutes) > > I know there are a few Twitter push clients for iPhone , but none of > them can work on a scaled user base, am I right? > > Is there a twitter tech support here? could you please give some > suggestions? >
[twitter-dev] OAuth - get_request_token - 401 Unauthorized - ruby gem
Hi,
I've recently started to get 401 Unauthorized errors from twitter
while trying to get a request token.
I'm using the OAuth Ruby gem and making the request from irb as
follows:
OAuth::Consumer.new(our_secret, our_key,{ :site=>"http://
twitter.com" }).get_request_token()
I've made the request from several different machines and got a good
request token back from twitter, but it seems to be giving the 401
errors only on our production server. This used to work fine on this
machine until recently.
Is there still currently ongoing problems with the twitter api in this
regard?
Thanks,
Julian
[twitter-dev] Re: Platform Status Update, Tuesday 2:00pm PST
Hi, I'm having the same issue form my iphone twitter app, I'm deleting status via http://www.twitter.com/statuses/destroy/id.xml and I'm always getting a status 400 error which my app displays to the user even though the status was deleted. is this a permanent change to the API?? thanks, Matt On Aug 19, 4:49 pm, deepikagupta wrote: > Hi, > > I am facing problem while Deleting any Tweet from my > application.http://www.twitter.com/statuses/destroy/id.xmlalways gives me400 > status code but also deletes the tweet. So in my application it is > caught as an exception only and error message is shown to user even > though tweet is deleted. > I am facing this issue only while deleting tweets and mentions. HTTP > request for delete seems to be working fine with direct messages and > favorites. > > Please Help me!!! > > On Aug 19, 8:46 am, djc8080 wrote: > > > > > Oops. spoke too soon. Still eradic problems - same symptoms. Incorrect > > rate_limit response on statuses/followers when ..ids calls work > > perfectly on the same account.
[twitter-dev] Re: Developer Preview: Geolocation API
Crazy I just read same sentence / tech concept in a PDF called SocialInfluenceEC thanks to the 3 publishers. If any are here, I'd like to work with a team or group that actually acts and defines the level such as diffusion, scoring, tracking paths, distance, etc etc cell 917 512 6281 On Aug 21, 2009, at 4:54 AM, Sean dCallahan wrote: > > Quick question Ryan, because none of this will surface on Twitter.com > will you keep the Location field for a users profile or is that going > away when this becomes love? If it stays, will there be any specific > changes regarding the location on a user's profile when this API > becomes available? > > Sean > > On Aug 20, 5:28 pm, Lepton wrote: >> Perfect timing! My iPhone app about to be released has a lot to do >> with geolocation, and already uses Twitter to set and see locations >> of >> people. Myallo HotList tracks the "hotness" of people and places in >> your social universe partly through their locations. For example as a >> person gets nearer to you, they get hotter, if friends gather near a >> place, they and the place get hotter. I want to use these upcoming >> features to "discover" nearby people. You can preview the app via its >> documentation athttp://myallo.com/hotlist
[twitter-dev] Re: how can I get user address using Twitter API?
no, on purpose. On Fri, Aug 21, 2009 at 01:08, Bo Huang wrote: > > Hi, > > I am trying to integrate Twitter OAuth with my website. Right now I > can use this API (https://twitter.com/account/verify_credentials.xml) > to get lots of profile information like user ID, screen name, but I > didn't any info about the user email address. Is there any API to get > email address? Thanks in advance. > > Bo > -- Internets. Serious business.
[twitter-dev] Re: Developer Preview: Geolocation API
Cool indeed. Speaking of GeoRSS: why enclose georss:point within a new "geo" element? Why not use georss:where? On Aug 21, 12:32 am, Nelson Minar wrote: > Very exciting! Thanks for giving the community an early preview. > > GeoRSS supports altitude and accuracy measures for point locations as > well. in GeoRSS-Simple, it's something like > > 45.256 -110.45 > 500 > 313 > > (at that lat/long, within 500 meters, at an elevation 313 meters above > the WGS84 ellipsoid). > > Any plan to support that in the Twitter API? Radius is very useful for > dealing with inaccurate geolocation, and elevation (or ) > can help distinguish exactly where someone is. > > These links may be relevant to the discussion: > > W3C Geolocation API:http://dev.w3.org/geo/api/spec-source.html > (Javascript API to location. Safari supports this nicely on the > iPhone.) > > iPhone CLLocation > API:http://developer.apple.com/iphone/library/documentation/CoreLocation/... > > Both APIs specify position as latittude, longitude, horizontal > accuracy, altitude, and vertical accuracy.
[twitter-dev] Re: Developer Preview: Geolocation API
Hi, Please could you advise on the differences between this and the current location based searching facility? Is the current location search based on the users location in their settings whilst this is a exact location for each tweet? Thanks, Ben On 20 Aug 2009, at 21:46, Ryan Sarver wrote: > We wanted to give you all a heads up on a cool new feature that is > coming soon - Geolocation. The Geolocation API will give us the > ability to attach geographic metadata to tweets to provide > additional context with your update. Along with the option to tag > updates, we will be able to search for nearby tweets and view the > geo metadata in user timelines. The additional context allows for us > to deliver more meaningful and localized experiences to users. We > are also really excited about a unique facet of this release in that > it will be API-only initially. This means that Twitter.com won't > surface the functionality and we look forward to seeing the new and > interesting experiences that will grow out of the ecosystem. > > As part of our Geolocation efforts we will soon be publishing > "Geolocation Best Pracitices" to guide everyone through issues like > security and privacy as well as discussing some ideal experiences > for users. Topics will include things like storage of location data, > what to do with a user's historical data, how to present the concept > of geotagging and more. The guide will create a framework from which > we can address the challenges that come about when dealing with > something as sensitive as someone's location while hopefully > allowing everyone enough creative freedom to create their own > experiences around it. > > It is important to note that the feature is going to be strictly opt- > in. It will be disabled until a user chooses to switch it on. We > will provide a read-only attribute on the user object > so an app can detect if the user has it disabled and let them know > if they need to turn it on before using a geolocation feature. > > While we can't provide an exact date for launch, you should plan on > having a few weeks of development time before the new API is > officially launched. With that being said, lets get to it... > > Example: Geotagging a Tweet > --- > curl -d "lat=37.780467&long=-122.396762&status=I have arrived" -u > user:pass "http://twitter.com/statuses/update.xml"; > > > > > > Tue Apr 07 22:52:51 + 2009 > > ... > > http://www.georss.org/georss";> > > 37.780467 -122.396762 > > > > > > 1401881 > > Doug Williams > > ... > > true > > ... > > > > > > > We have also updated the wiki to reflect what the API will look like > when it launches, so check it out and let us know if you have any > questions: > http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update > http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials > > We'll also be in our recently announced IRC channel (#twitterapi on > irc.freenode.net) if you want to discuss the announcement with the > team. > > Ryan > > PM, Platform Team > http://twitter.com/rsarver
[twitter-dev] Re: large user base push notification solutions?
On Aug 21, 12:06 am, "ke...@nibirutech.com" wrote: > What if we have a large user base, say , 500, 000 users at > least? How can we use a proper solution to get a 2-minutes delay push > for any user's mentions and DMs? (we can't afford the server cost for > half million requests every 2 minutes) You are actually talking about one million API calls every 2 minutes (1 for mentions, one for DMs). That's 8,300 API calls per second. My rough estimate is that you are going to need around 200 servers to cope with that workload. Dewald
[twitter-dev] Re: Search API sometimes returning random tweets mixed in?
Yes, earlier in the week we saw a lot of these reported by TweetDeck users too. Seems to have tailed off now though. On Aug 20, 4:42 pm, Marco Kaiser wrote: > Hi, > we are receiving an increasing number of reports from users about search > results containing tweets that don't match the search query. It doesn't seem > to be reproducable, i.e. a later request for the same query does not contain > the false results. We've also seen from user reports on twitter that other > clients seem to be affected. > > Anyone got an idea what's going on? Or can someone confirm that he's also > running into that issue? > > Thanks, > Marco
[twitter-dev] how can I get user address using Twitter API?
Hi, I am trying to integrate Twitter OAuth with my website. Right now I can use this API (https://twitter.com/account/verify_credentials.xml) to get lots of profile information like user ID, screen name, but I didn't any info about the user email address. Is there any API to get email address? Thanks in advance. Bo
[twitter-dev] incomplete json response from twitter search query
I used the twitter API search query "maker" to create a query. In a
browser it returns a JSON file with the expected amount of entries for
the first page. I use the same url query with my javascript
application using an Ajax.Request. This returns only about two entries
and a half entries and the last entry is not complete. I should get 50
entries from the first Ajax request. I do get 50 entries from the
browser for the same query. Here is the code - is there a parameter
I'm missing in either the url or the Ajax request? Any recommendations
or suggestions would be appreciated. thanks, James
Assistant.prototype.twitterRequest = function(){
url="http://search.twitter.com/search.json?q=&ands=&phrase=&ors=
%24BAC+%24BTU+
%24LLY¬s=&tag=&lang=en&from=&to=&ref=&near=&within=15&units=mi&since=&until=&rpp=50";
new Ajax.Request(url, {
method: 'get',
requestHeaders: {
Accept: 'application/json'
},
onSuccess: function(transport){
var json = transport.responseText;
}
})
};
[twitter-dev] Re: large user base push notification solutions?
If you're already talking about a 2-minute delay, then why "push" and not "pull" ?? Polling clients will give you greater scalability with that range of latency easily achievable for little investment. Push is meant for immediate notifications. True push to 500k+ clients is costly -- but you don't need millisecond latency here. Pull is much, much cheaper. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera) On Fri, Aug 21, 2009 at 8:07 AM, Dewald Pretorius wrote: > > In addition, your database will have to cope with 8,300 writes per > second. And then you need to take into account the latency of the > Apple Push Notification service. > > Dewald > > On Aug 21, 8:57 am, Dewald Pretorius wrote: >> On Aug 21, 12:06 am, "ke...@nibirutech.com" >> wrote: >> >> > What if we have a large user base, say , 500, 000 users at >> > least? How can we use a proper solution to get a 2-minutes delay push >> > for any user's mentions and DMs? (we can't afford the server cost for >> > half million requests every 2 minutes) >> >> You are actually talking about one million API calls every 2 minutes >> (1 for mentions, one for DMs). >> >> That's 8,300 API calls per second. >> >> My rough estimate is that you are going to need around 200 servers to >> cope with that workload. >> >> Dewald >
[twitter-dev] Twitter Not displaying russian character posted through Twitter API
Hi, We have developed a website http://www.sekretanet.ru. Everything is fine . The web site has tweet post can option. But when we tweet english posts it just dispalys on Twitter fine. But when we Tweet Russian Language post Twitter do not display russian characters correctly. www.twitter.com/skeretanet. to see . Furhter we are usifn charset as utf-8 and we do use utf-8encode function of php. Is there any help ?? . I will very appreciate it. Wajahat ali Developers of Site http://www.sekretanet.ru
[twitter-dev] Re: large user base push notification solutions?
In addition, your database will have to cope with 8,300 writes per second. And then you need to take into account the latency of the Apple Push Notification service. Dewald On Aug 21, 8:57 am, Dewald Pretorius wrote: > On Aug 21, 12:06 am, "ke...@nibirutech.com" > wrote: > > > What if we have a large user base, say , 500, 000 users at > > least? How can we use a proper solution to get a 2-minutes delay push > > for any user's mentions and DMs? (we can't afford the server cost for > > half million requests every 2 minutes) > > You are actually talking about one million API calls every 2 minutes > (1 for mentions, one for DMs). > > That's 8,300 API calls per second. > > My rough estimate is that you are going to need around 200 servers to > cope with that workload. > > Dewald
[twitter-dev] Re: URGENT HELP NEEDED
As long as your app is registered with Twitter with an appropriate
name, and you're using your consumer key and secret, the "from
[yourapp]" should be automatic with OAuth. If it's not, it's probably
a bug/temporary issue. I'm using OAuthBase.cs myself with no problems
with source at the moment:
http://twitter.com/andrewbadera/status/3447332737
However, is what you provide all of your code? With OAuth you don't
use the username/password, you use the authorization URL to pass the
user to Twitter, where they can approve access for your app. Twitter
then redirects them back to your callback url (which you can provide
at call time as oauth_callback rather than use the setting in the
Twitter application registry) where it also POSTs the access token and
secret for the user.
You then make your request using your consumer token values PLUS the
user token values. Your token values identify your service or app, the
user token identify the user. Username/password is only for Basic
Auth, and Basic Auth only shows "from [app]" if the app predates
OAuth. Http Basic is in the process of slowly, slowly being
deprecated. When you provide the username/password but not the user
token/secret, I believe that class defaults to Http Basic Auth.
∞ Andy Badera
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
On Thu, Aug 20, 2009 at 8:27 AM, Kuntal wrote:
>
> Hello All,
>
> I want to show updates are instead of
> "from web"
>
> We want to integrate the status update system of twitter in our web
> application which is made in .NET Framework 2.0. We have integrated it
> successfully and is updating the status. But the problem we are facing
> that the message says. "from Web".
>
> We want to make it "from ". For that we have registered
> our application in twitter.
>
>
> It provided us the following information...
>
> 1) Consumer key
> 2) Consumer secret
> 3) Request token URL
> 4) Access token URL
> 5) Authorize URL
>
> We are using the API and is using the following code.
>
>
> public void Test()
> {
>
> OAuth_Twitter obj = new OAuth_Twitter();
>
> obj.strusername = "";
> obj.strpassword = "";
>
> obj.consumerKey = "";
> obj.consumerSecret = "";
> obj.token = obj.AuthorizationLinkGet();
>
> obj.oAuthWebRequest("POST", "https://twitter.com/statuses/
> update.xml", "status=" + "" + "&source=my_app");
> }
>
>
> Please look at above code. We have two class file also. Those are
> "OAuth_Twitter.cs" and "OAuthBase.cs". In the above code please look
> that we have used "source=my_app" to make from "from Web" to "from
> ". We got this suggestion from many sites as they
> suggested. But we are so sorry that we could not reach to our
> objective.
>
> Please help us out to solve our problem. We are eagerly waiting for
> your reply.
>
> Thanks
>
[twitter-dev] Re: Developer Preview: Geolocation API
Quick question Ryan, because none of this will surface on Twitter.com will you keep the Location field for a users profile or is that going away when this becomes love? If it stays, will there be any specific changes regarding the location on a user's profile when this API becomes available? Sean On Aug 20, 5:28 pm, Lepton wrote: > Perfect timing! My iPhone app about to be released has a lot to do > with geolocation, and already uses Twitter to set and see locations of > people. Myallo HotList tracks the "hotness" of people and places in > your social universe partly through their locations. For example as a > person gets nearer to you, they get hotter, if friends gather near a > place, they and the place get hotter. I want to use these upcoming > features to "discover" nearby people. You can preview the app via its > documentation athttp://myallo.com/hotlist
