[twitter-dev] Getting error "The remote name could not be resolved: 'api.twitter.com' " while twitting data from my website
Hi.
I am using Twitterizer Aouth API.
Below is the code which I am using to connect to twitter from my website.
stringconsumerKey = ConfigurationManager.AppSettings["consumerKey"];
string consumerSecret = ConfigurationManager.AppSettings["consumerSecret"];
if (System.Web.HttpContext.Current.Request.QueryString["oauth_token"] ==
null)
{
RequestToken = OAuthUtility.GetRequestToken(consumerKey, consumerSecret,
_currentURL);
System.Web.HttpContext.Current.Response.Write("window.open('<a rel="nofollow" href="http://twitter.com/oauth/authorize?oauth_token="+">http://twitter.com/oauth/authorize?oauth_token="+</a>
RequestToken.Token +
"','_new','height=500,width=850,status=yes,resizable=yes');window.location.href=window.location.href;"
);
}
Some times I get The remote name could not be resolved: 'api.twitter.com'
exception when my website tries to connect to twitter using above code.
Can some one please help me in this?
Thanks,
Richard
--
Have you visited the Developer Discussions feature on
https://dev.twitter.com/discussions yet?
Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi
Unsubscribe or change your group membership settings:
http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Twitter group API
Does anyone know if there is program available to create several groups using one Twitter account and allowing you to message each of those groups individually? For example - Twitter.com/username Group 1 (100 followers) Group 2 (56 followers) Group 3 (77 followers) I would like to send separate messages to each of those groups. Please let me know if you know of any way to do this via API or a 3rd party program. Thank you. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] http://m.twitter.com/oauth/authorize is redirecting to https://mobile.twitter.com/
http://m.twitter.com/oauth/authorize is currently redirecting to https://mobile.twitter.com/. Earlier today I saw it redirecting to http://m.twitter.com/oauth or https://m.twitter.com/oauth (in the latter case via a certificate warning). http://twitter.com/oauth/authorize is behaving as expected. I assume this is some transient problem caused by some certificate/subdomain shakeup? If so, can anyone from Twitter provide an estimated time for a fix? (I just tried using mobile.twitter.com/oauth/authorize and ended up at https://mobile.twitter.com/oauth.) Thanks -- Richard -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Twitter feed for corporate website/portal
Peter Denton, I have a corporate website and I would like to show Twitter feeds of my selected keywords (Theme Based). For that I would like to use API which get me the feeds directly..without creating any Twitter account, just like anonymous user..my question is, will Twitter consider it as SPAM.. Or Shall I follow 1. Get the feed or /statuses/user_timeline without authentication at a rate up to 150 times per hour and store the tweets in a database. Then serve tweets to your web page from the database. Thanks for any help on this. On Jan 12, 9:15 am, Peter Denton wrote: > also, check out Twitter Widgets. You can pull in tweets based on search, > profile, or list-- so you might be able to use that. > > Since the request is client side, rate limiting is not going to be as big of > an issue. You could also completely customize the UI if needed, both through > the form Twitter provides to generate the UI as well as with plain old css. > > http://twitter.com/about/resources/widgets > > If you need any help, I would be happy to help you off the list. > > > > On Tue, Jan 11, 2011 at 8:08 PM, Adam Green <140...@gmail.com> wrote: > > You can use the /statuses/user_timeline API call instead of the feed if you > > want. This doesn't require authentication, so there is no need to create an > > app, if you use this call: > >http://dev.twitter.com/doc/get/statuses/user_timeline > > > But no matter how you get the data, rate limiting will still be the same. > > There are three ways to address rate limiting: > > 1. Get the feed or /statuses/user_timeline without authentication at a rate > > up to 150 times per hour and store the tweets in a database. Then serve > > tweets to your web page from the database. > > 2. Create an app that uses OAuth to get the feed or /statuses/user_timeline > > at a rate up to 350 times per hour. Store and serve from DB as in 1. > > 3. Use the Streaming API to follow the user account. This uses Basic Auth, > > so no app is needed. Get the data, store and serve from DB. The streaming > > API has the advantage of delivering the data in real time with no rate > > limiting. > > > The point here is that each page load should not call Twitter for data. It > > should call for your copy of the data. > > > If you decide to use 2, you do need an app to do OAuth. From my experience, > > the app registration page needs a properly formatted URL, not a valid URL > > that you own. This means anything that follows the format of > >http://domain.comwill work. You can even usehttp://twitter.com. > > -- > > Adam Green > > Twitter API Consultant and Trainer > >http://140dev.com > > @140dev > > > On Tue, Jan 11, 2011 at 7:43 PM, TehOne wrote: > > >> I have a corporate website/portal that I want to pull in tweets to, > >> but i'm getting a rate limit using the http feed. So I need to explore > >> other options. Do I need to use an authenticated method to get the > >> tweets? > > >> Do I really have to register an application to do this, even though > >> it's not really an application and my users will never be entering or > >> changing the twitter account info. It will be a single twitter account > >> that I will be pulling the feed from. > > >> Also, my corporate site doesn't have a public address, and registering > >> an application through twitter appears to require a public url. So how > >> can I get around this? Do I have to create a "fake" application with a > >> public url, just to generate my keys? > > >> Thanks for any help on this. > > >> -- > >> Twitter developer documentation and resources:http://dev.twitter.com/doc > >> API updates via Twitter:http://twitter.com/twitterapi > >> Issues/Enhancements Tracker: > >>http://code.google.com/p/twitter-api/issues/list > >> Change your membership to this group: > >>http://groups.google.com/group/twitter-development-talk > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk > > -- > Peter Denton > Co-Founder, Product Marketingwww.mombo.com > cell: (206) 427-3866 > twitter @Mombo_movies > twitter - personal: @petermdenton -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Can twitter tell me when there is a new tweet?
Just got twitter posting working on my site. I now want to read a users tweets. From what I can see (documentation layout is awful) I can only do this by polling twitter. Is there a way to get twitter to call my callback url for my app when any of the users that have ok'd it tweets? That is, push instead of pull. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Error messages during authorize and redirect processes (OAuth)
On Aug 27, 11:16 am, Matt Harris wrote: > To allow us to track the issue and to make sure it gets fixed can you > file a bug report on our issues list: > http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/detail?id=1827 -- R -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Error messages during authorize and redirect processes (OAuth)
On Jul 7, 9:07 pm, Andy wrote: > Bad: At Google Chrome browser (Version 5.0.375.99) it shows error, > when I go to authorize-page (with question "Connect your account?") at > retweet: > > Here is the complete error message: > > - > This page contains the following errors: > error on line 393 at column 41: Entity 'rarr' not defined > Below is a rendering of the page up to the first error. > - > > At lines 391 - 393 stands: > > > Zugreifen und aktualisieren? → > I just hit the same problem with Chrome, on the English version of the OAuth authorise page http://m.twitter.com/oauth/authorize. I'm sure that if Chrome disagrees with → then many mobile browsers are also likely to have trouble with it too. Is this likely to be fixed soon? -- Richard -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Trends-API not working
Allow me to correct the message above: http://search.twitter.com/trends.json?date=2010-06-14 On Jun 14, 5:15 pm, Richard Coleman wrote: > Try this one instead: > > http://search.twitter.com/trends.json?date=2010-03-05%20 > > On Jun 14, 10:24 am, "dennisp@web.de" wrote: > > > > > Hi, > > > I got a problem using the Twitter-API, especially the Trends-Data. > > When calling the > > URLhttp://search.twitter.com/trends/daily.json?date=2010-03-05 > > (or another date), i just get an empty JSON-object back. If I use the > > new URLhttp://api.twitter.com/1/trends/daily.json?date=2010-03-05I > > always get a 404 - Not Found Exception. Some dates return a non-empty > > JSON-string, but most of them do. > > The last time I used the API everything works fine, but after not > > looking for it for a few weeks, I ran into this trouble. > > > Does anyone have these troubles, too?
[twitter-dev] Re: Trends-API not working
Try this one instead: http://search.twitter.com/trends.json?date=2010-03-05%20 On Jun 14, 10:24 am, "dennisp@web.de" wrote: > Hi, > > I got a problem using the Twitter-API, especially the Trends-Data. > When calling the > URLhttp://search.twitter.com/trends/daily.json?date=2010-03-05 > (or another date), i just get an empty JSON-object back. If I use the > new URLhttp://api.twitter.com/1/trends/daily.json?date=2010-03-05I > always get a 404 - Not Found Exception. Some dates return a non-empty > JSON-string, but most of them do. > The last time I used the API everything works fine, but after not > looking for it for a few weeks, I ran into this trouble. > > Does anyone have these troubles, too?
[twitter-dev] Re: statuses/update: Expect: 100-Continue header rejected
On May 20, 10:38 pm, Cameron Kaiser wrote: > > I've been playing with > > oacurlhttps://code.google.com/apis/buzz/v1/oacurl.html > > and tried to use it to send a tweet. > > > oacurl sends Expect: 100-Continue but Twitter rejects this with "we > > only allow the 100-continue expectation". > > > Is this fixable, or avoidable in the meantime? (I know about twurl, > > but oacurl seems generic - can I use twurl to make oauth calls to > > MySpace?) > > Just change the header to simply send a blank "Expect:". With regular > cURL a simple -H "Expect:" will work. Thanks for your reply. Although oacurl supports -H like curl, using -H "Expect:" adds a second Expect: header to the request, & the Twitter server still fails because of Expect: 100-Continue. I'll raise the oacurl bug with one of the authors, but that still leaves a bug in Twitter's handling of Expect:. /c/download: echo "status=Testing+oacurl" | java -cp oacurl-1.0.0.jar com.google.oacurl.Fetch -X POST -H "Expect:" -v http://api.twitter.com/1/statuses/update.json > POST /1/statuses/update.json HTTP/1.1 > Content-Type: application/atom+xml > Expect: > Authorization: OAuth > oauth_token="34507306-fJYSoMdju3Vv9SecfdyCUbYu5JdlIPLyaVN3xElNw", > oauth_consumer_key="FFUZwLopTkug9Dlj1KamA", > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1274396737", > oauth_nonce="571291495191528", oauth_version="1.0", > oauth_signature="CqiI%2FY%2Br96PGVPkCSClqnkmfHAo%3D" > Transfer-Encoding: chunked > Host: api.twitter.com > Connection: Keep-Alive > User-Agent: Apache-HttpClient/4.0 (java 1.5) > Expect: 100-Continue > status=Testing+oacurl[\n] -- Richard
[twitter-dev] statuses/update: Expect: 100-Continue header rejected
I've been playing with oacurl https://code.google.com/apis/buzz/v1/oacurl.html and tried to use it to send a tweet. oacurl sends Expect: 100-Continue but Twitter rejects this with "we only allow the 100-continue expectation". This seems to violate http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.20 "Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token)". Is this fixable, or avoidable in the meantime? (I know about twurl, but oacurl seems generic - can I use twurl to make oauth calls to MySpace?) Output from oacurl (duplicate content snipped) is below: /c/download: echo "status=Testing+oacurl" | java -cp oacurl-1.0.0.jar com.google.oacurl.Fetch -X POST -v http://api.twitter.com/1/statuses/update.json > POST /1/statuses/update.json HTTP/1.1 > Content-Type: application/atom+xml > Authorization: OAuth oauth_token="34507306-x", > oauth_consumer_key="x", oauth_signature_method="HMAC-SHA1", > oauth_timestamp="1274334015", oauth_nonce="508570714177400", > oauth_version="1.0", oauth_signature="x" > Transfer-Encoding: chunked > Host: api.twitter.com > Connection: Keep-Alive > User-Agent: Apache-HttpClient/4.0 (java 1.5) > Expect: 100-Continue < HTTP/1.1 417 Expectation Failed < Date: Thu, 20 May 2010 05:38:21 GMT < Server: hi < Vary: Accept-Encoding < Content-Length: 364 < Connection: close < Content-Type: text/html; charset=iso-8859-1 417 Expectation Failed Expectation Failed The expectation given in the Expect request-header field could not be met by this server. The client sent Expect: 100-Continue but we only allow the 100-continue expectation. -- Richard
[twitter-dev] Re: Mobile OAuth Summary
On Apr 30, 5:52 pm, "bob.hitching" wrote: > At Xumii we’re using Twitter mobile oAuth on a wide range of phones, > from low-end feature phones to high-end smartphones. A recent QA cycle > revealed 7 out of 30 Most Popular devices not coping with Twitter > mobile oAuth: Samsung C3110, Nokia 3120, SE G502, SE C905, LG KU990, > Nokia N96, SE W705. Our Xumii products would also benefit from MobileOK-compliant protected Twitter account pages on m.twitter.com or mobile.twitter.com. I raised this in http://groups.google.com/group/twitter-development-talk/browse_frm/thread/f41e4299a646520b but there was no resolution. -- Richard
[twitter-dev] Re: Mobile view of twitter.com doesn't show "This person has protected their tweets" message
On Apr 8, 1:41 am, Abraham Williams <4bra...@gmail.com> wrote: > Have a look at the new http://mobile.twitter.com. It looks awesome and > displays if profiles are protected. It does look awesome; unfortunately it uses a bunch of Javascript which (in general) many low-end mobile browsers can't handle. I need a mobile-optimised Javascript-free page that displays the "protected" message. -- Richard
[twitter-dev] Mobile view of twitter.com doesn't show "This person has protected their tweets" message
For the case where I'm trying to view a protected Twitter account profile http://twitter.com/username & I'm not signed in or not a follower: - "Standard" view displays a page with a lock image & the message "This person has protected their tweets" - "Mobile" view displays a page with a message "This functionality is not currently supported in the mobile site. This is coming soon. Thanks for your patience!" This occurs in FF, IE, Chrome & Opera. This is confusing to users of the app I'm developing, which renders a mobile-optimised webpage with links to http://m.twitter.com/username. Is this likely to be fixed any time soon? Thanks -- Richard Barnett -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: Most popular tweets in the search API
I'm also curious to understand how 'popular' tweets will be determined. Once a tweet is considered to be popular for search purposes, might it be cached for an extended period of time so that it will return for queries beyond the currently limited period? -- Richard Nevins Twitter: @hornOKplease To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] Re: Introduce yourself!
Hi I'm Richard Cunningham. PHP/MySQL coder, Linux Sys. admin and creator of http://friendbinder.com a site to bring all your friends into one place, currently supporting Twitter, Facebook, Flickr, Digg, RSS and others. I've been working with the Twitter API since 2008. Richard Cunningham http://twitter.com/rythie
[twitter-dev] Re: REST API authentication not being recognized on a different server
This might be also related to this http://code.google.com/p/twitter-api/issues/detail?id=1439&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component We are seeing lots of people unable to validate their credentials via basic auth after changing their twitter password. On Feb 11, 12:24 am, Aaron Chu wrote: > Our authentication is not working on our production server which > defaults us to the 150 calls/hour. However, our test server > authenticates just fine and we are getting the full 20,000 there. This > problem recently came up after changing our password. We are using > curl -u user:passwordhttp://twitter.com/account/verify_credentials.xml > to check the authentication.
[twitter-dev] Re: Rate limit HTTP response
We see quite a few TweetDeck users complaining of mysterious 0 API limits here. No other apps in use and very few API calls made, suddenly down to 0. Looks to be some kind of API issue here... On Jan 27, 11:59 pm, EastSideDev wrote: > Prior to doing a rate-limit API, I always get > thehttp://twitter.com/account/rate_limit_status.xml(using my > credentials). Every once in a while, I get an HTTP response code of 0 > (even though the previous call may have told that I still have more > than 19,000 calls left. My workaround is is do..while loop, with a > break of 10 loops. > > Any suggestions?
[twitter-dev] Re: Suggestion: Ability to just search amongst a user's friends
We now have this in friendbinder.com - though unfortunately we don't currently have an API. On Nov 3, 5:35 pm, yoni wrote: > This functionality would be *huge*. Likewise, it'd be great if we > could search lists. Now that we have 'em, it'd be great to use lists > as filters for search. > > So, in the current search API, we've got from:USER, it'd be great if > we could have in:LIST or some such. > > Thanks! > > ~ yoni > > On Oct 27, 11:02 pm, Chad Etzel wrote: > > > > > This is something that we're considering internally. I'll bring it up again, > > though. > > > -Chad > > > On Tue, Oct 27, 2009 at 11:33 PM, Jesse Stay wrote: > > > I have a project in which it would be tremendously easier if I could just > > > specify a search to take place amongst a particular user's Twitter > > > friends, > > > instead of across the entire site. Is there a way to do this currently? > > > If > > > not, is this something the team could consider? I can make it work by > > > comparing the full results to a list of friends, but that seems like > > > unnecessary work. > > > > Thanks, > > > > Jesse
[twitter-dev] Re: searching spesific keyword in Tweets
You can also try friendfeed, if the people you are searching for joined it, they have it going a long way back On Dec 16, 3:18 pm, dbasch wrote: > You can also try search.trendistic.com . We have a fraction of the > tweets but you can search all of 2009. > > On Dec 16, 11:29 am, John Kalucki wrote: > > > > > Google.com is your only bet, and it will be very patchy. > > > -John Kaluckihttp://twitter.com/jkalucki > > Services, Twitter Inc. > > > On Tue, Dec 15, 2009 at 9:50 PM, MuratMetu wrote: > > > Hello, I am new to Twitter development. Is there any way to get all > > > tweets including specific keyword "x" ans posted in the most recent 3 > > > - 4 months. I heard that there is a way to do it for 1-2 week old > > > tweets but I need to go 3-4 months back. Thank you.
[twitter-dev] Re: Status update 11:27pm PDT
Is this the DNS issue? Do you know the precise times the site was compromised for? Also should we be worried that apps not using oAuth will have sent passwords to some other site? On Dec 18, 7:28 am, Ryan Sarver wrote: > Just wanted to drop an email to everyone and let you know that we are > investigating the issue and will follow up with more details as we > determine the cause and are able to share information. > > Thanks for your patience, Ryan
[twitter-dev] Re: Making crossdomain.xml less restrictive on api.twitter.com?
Chad Etzel wrote: > After discussing this internally, we have decided that we will make > thecrossdomain.xml policy more open on the api.twitter.com domain. We > don't know exactly what that entails yet or when it will go into > effect, but this is something that we want to open up. Another +1 on this. I'm about to deploy a Flash app giving users the option to send tweets and which will have to use a proxy for now. I really don't like doing this as there's always the suspicion that I could use it to harvest users' names and passwords - though of course I'm not doing! A permissive crossdomain.xml would be a huge boost. Richard
[twitter-dev] Re: New cursor methods are way too slow
I've got the same problem too with this. We were parallel fetching the
friends list but this new method is going to be too slow and I agree
with Josh that "we really need a way to bulk request user payloads by
giving a list of IDs"
On Oct 22, 2:10 pm, Harshad wrote:
> Exactly the same scenario here [1] too. Querying with Bulk Ids would
> save quite a bit of overhead for both parties.
>
> Btw, if so many people are doing this graph-walking exercise, how
> about collaborating and sharing this data? Feel free to contact me off-
> list at { harshad.rj AT gmail }
>
> [1]http://twinkler.in
>
> On Oct 21, 4:23 pm, Oren Rose wrote:
>
> > I vote for that, too!
>
> > Same scenario, same issues... bulk status request is the right
> > solution, also for users you get from the Search API...
>
> > = Oren
>
> > On Oct 20, 8:02 pm, Michael Steuer wrote:
>
> > > Hi,
>
> > > The reason why I¹m using followers/ids and then users/show is efficiency:
>
> > > I¹m maintaining a local cache of my users social graph. I¹m also
> > > maintaining
> > > local user objects for my users and for their followers. Since both the
> > > social graph and user info are subject to change, both need periodic
> > > updating... They way I¹m doing that now is as follows:
>
> > > 1. I request followers/ids for each of my users
> > > 2. If I detect new followers I add them to my users social graph / If I
> > > detect followers removed, I remove them from my users social graph
>
> > > Subsequently I parse my user object table for users whose:
> > > 1. info hasn¹t been updated in X days
> > > 2. have no info because they were added as numeric IDs only via the
> > > followers/ids method described above
>
> > > I then request users/show for each user matching condition 1 or 2 above.
>
> > > This way, I only get an updated user object for each unique user once,
> > > when
> > > they¹re first added, or when I expire a previous update to their info.
> > > When
> > > I get the followers of another new user, chances are I already know the
> > > majority of his followers user information.
>
> > > I¹m not using statuses/followers because I would be getting the same
> > > information over and over and over and over again... Especially when
> > > you¹re
> > > talking about users with a lot of followers, it¹s really inefficient
> > > considering you probably already store user info on most of the user¹s
> > > followers... It would be an equally efficient method if overlap in
> > > followers
> > > didn¹t exist... Since it does, I believe my approach is more efficient,
> > > and
> > > faster over time, as your user database grows and your basically just
> > > querying the social graph...
>
> > > ALL THAT SAID I would LOVE to have a method that allows me to get user
> > > objects in batch... If I could request 100 user objects by numeric id in
> > > one
> > > API call, the above would be exponentially efficient and result in far
> > > fewer
> > > calls to Twitter.
>
> > > I am definitely interested in your feedback on my logic above and if you
> > > think it holds...
>
> > > Thanks!
>
> > > Michael.
[twitter-dev] Re: Problems Connecting to the API
I'm getting this from my slicehost servers. $ traceroute twitter.com traceroute to twitter.com (168.143.161.20), 30 hops max, 40 byte packets 1 67-207-128-2.slicehost.net (67.207.128.2) 0.191 ms 0.165 ms 0.153 ms 2 209-20-79-2.slicehost.net (209.20.79.2) 0.704 ms 0.776 ms 0.347 ms 3 ge-6-10-163.car1.StLouis1.Level3.net (4.53.160.241) 1.813 ms 1.747 ms 1.720 ms 4 ae-11-11.car2.StLouis1.Level3.net (4.69.132.186) 1.678 ms 1.680 ms 1.863 ms 5 ae-4-4.ebr2.Chicago1.Level3.net (4.69.132.190) 14.920 ms 14.921 ms 14.899 ms 6 ae-2-56.edge3.Chicago3.Level3.net (4.68.101.180) 21.901 ms ae-2-52.edge3.Chicago3.Level3.net (4.68.101.52) 21.860 ms ae-2-54.edge3.Chicago3.Level3.net (4.68.101.116) 7.653 ms 7 4.68.63.198 (4.68.63.198) 8.226 ms 7.614 ms 8.172 ms 8 ae-1.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.8) 7.824 ms 7.650 ms 7.420 ms 9 as-1.r21.dllstx09.us.bb.gin.ntt.net (129.250.3.17) 30.882 ms 33.149 ms 33.468 ms 10 po-2.r01.dllstx09.us.bb.gin.ntt.net (129.250.4.42) 33.440 ms 33.412 ms 33.027 ms 11 * * * It's working from Freedom2surf ADSL in the UK. On Oct 18, 3:31 pm, Michael Steuer wrote: > On my end: my server (at Rackspace) can't connect to twitter.com... If I > enter API URLs into my browser at home (Verizon DSL), I connect just fine. > Here's a traceroute from rackspace: > > traceroute twitter.com > traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets > 1 xxx-xxx-xxx-xxx.static.cloud-ips.com (xxx.xxx.xxx.xxx) 4.000 ms 4.000 > ms 4.000 ms > 2 98.129.84.216 (98.129.84.216) 0.000 ms 0.000 ms 0.000 ms > 3 edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115) 4.000 ms > 4.000 ms edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113) 4.000 > ms > 4 dls-bb1-link.telia.net (213.248.88.173) 4.000 ms 4.000 ms 4.000 ms > 5 verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62) 96.005 ms 96.005 > ms 96.005 ms > 6 * * * > > Based on my logs, this has been going on since before 2AM PST > > On Sun, Oct 18, 2009 at 7:23 AM, Dewald Pretorius wrote: > > > traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte > > packets > > 1 81.b5.85ae.static.theplanet.com (174.133.181.129) 1.351 ms 1.439 > > ms 1.464 ms > > 2 et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5) 0.198 ms 0.229 > > ms 0.266 ms > > 3 et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154) 0.444 ms > > et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157) > > 0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154) 0.466 ms > > 4 et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58) 0.519 ms > > et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169) 0 > > .454 ms 0.522 ms > > 5 xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5) 167.161 ms > > 167.045 ms 167.206 ms > > 6 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.185 ms > > 1.164 ms 1.180 ms > > 7 p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 6.424 > > ms 6.331 ms 6.358 ms > > 8 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 6.400 ms > > 6.451 ms 6.489 ms > > 9 * * * > > > -- > > > traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte > > packets > > 1 81.b5.85ae.static.theplanet.com (174.133.181.129) 0.387 ms 0.432 > > ms 0.475 ms > > 2 et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5) 0.211 ms 0.257 > > ms 0.273 ms > > 3 et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154) 0.472 ms > > et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157) > > 0.221 ms 0.249 ms > > 4 et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58) 0.404 ms 0.466 > > ms 0.553 ms > > 5 xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5) 107.597 ms > > 107.679 ms 107.742 ms > > 6 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.136 ms > > 1.114 ms 1.035 ms > > 7 p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 6.293 > > ms 8.708 ms 6.335 ms > > 8 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 6.433 ms > > 6.486 ms 6.535 ms > > 9 * * * > > > - > > > traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte > > packets > > 1 81.b5.85ae.static.theplanet.com (174.133.181.129) 0.429 ms 0.515 > > ms 0.567 ms > > 2 et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5) 8.956 ms 8.986 > > ms 9.024 ms > > 3 et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58) 0.439 ms 0.493 > > ms 0.546 ms > > 4 xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5) 1.156 ms > > 1.206 ms 1.254 ms > > 5 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.114 ms > > 1.113 ms 1.131 ms > > 6 p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 6.280 > > ms 6.256 ms 6.717 ms > > 7 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 6.377 ms > > 6.444 ms 6.499 ms > > 8 * * * > > > On Oct 18, 11:14 am, John Kalucki wrote: > > > I don't see any operational issues from here, but I'm not an > > > operational guy. At first glance the system looks fine, and the > > > operati
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Can this not be returned as hex or base64? It would save bandwidth for Twitter (and us) and make it a string people could convert it to 64bit int if they still want to. On Sep 25, 10:16 pm, Scott Haneda wrote: > I would not change either. But there are those here that are stating > they need new hardware to work around this issue, and that they can > not afford that. I was trying to be that voice of reason if that is > the road/excuse they are choosing to go. > > There seem to be acceptable workarounds, solid proposed workarounds, > etc. I guess I am not getting it, JSON is just a string returned, > yes, it can represent type of data, but it is still just a string. I > can not see it being that huge a performance hit to massage that > string a bit once you get ahold of it. > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > On Sep 25, 2009, at 2:02 PM, jmathai wrote: > > > It's ridiculous to suggest a change in hardware (64 bit) or software > > (switch from PHP) to use Twitter's API. It's not like either of these > > are archaic. It sucks, sure, but it's silly to suggest such a > > "solution". > > > BTW, I don't have this problem. I'm just trying to be the voice of > > reason.
[twitter-dev] Re: Alert: "Twitpocalypse II" coming Friday, September 11th - make sure you can handle large status IDs!
I note that this is when Twestival (http://twestival.com/) is on so a lot of developers maybe at events while this happens On Sep 9, 7:49 pm, Alex Payne wrote: > As mentioned previously, the Twitter operations team will artificially > increase the maximum status ID to 4294967296 this coming Friday, > September 11th. This action is part of routine database upgrades and > maintenance. > > If your Twitter API application stores status IDs, please be sure that > your datastore is configured to handle integers of that size. Thanks. > > -- > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly
I've seen many many reports of this coming in to TweetDeck support. Rate limit exceeded when it's not really. On Sep 8, 9:26 am, Reivax wrote: > I wish someone could just check this matter. > I can provide an XML file showing all ordered requests (with all > params, responses, etc) with the dumb counter values showing up. > > Thanks > Xavier > > On Sep 4, 11:37 am, Reivax wrote: > > > All requests are done authentified. > > > Thanks > > Xavier > > > On Sep 4, 11:26 am, fbparis wrote: > > > > According to the last api request you've done, X-RateLimit-Remaining > > > can be user limit or IP limit (depends if you made an authentified > > > request or not). > > > > This can explain the X-RateLimit-Remaining values you've posted. > > > > On Sep 4, 11:03 am, Reivax wrote: > > > > > I'm having this problem for a few days, and I've been monitoring ALL > > > > requests sent to twitter, here is what I saw : > > > > The value of the X-RateLimit-Remaining header is totally unreliable. > > > > For instance, the response to a request will have it at 120, while the > > > > next response will have it at 40. > > > > Then subsequent request responses will have values such as 118, 39, > > > > 37, 36, 117, ... and so on. > > > > > All responses have the same X-RateLimit-Reset ! > > > > > It all looks like there are 2 unsynchronized counters, and responses > > > > get values from either one of them... > > > > > The trouble is that one counter reaches 0 much too early, which makes > > > > my twitter client says the maximum allowed request has been reached !! > > > > > I make 3 requests every 2 minutes, so I should never reach the max. > > > > > I have the exact same behavior when using the rate_limit_status > > > > request. > > > > > I made sure I have no other client on that account, and I can > > > > reproduce the problem each time. Even if I had, there would not be > > > > cases where it goes from 36 to 117 for 2 adjacent requests... > > > > > Thanks for looking into that ! > > > > (I can provide traces of the requests) > > > > > Regards, > > > > Xavier
[twitter-dev] Re: OAuth changes?
I've been having some status updates fail using oAuth with .NET over the last few days. It seems to be an intermittent problem, and, like yours, my code's been working fine for months... Cheers, Rich. On Sep 5, 2:20 am, Bobby Gaza wrote: > Hi, > > I was curious if anyone has seen any calls to statuses/update stop > working usingOAuth/PHP Pecl. I recently started getting errors of > "Incorrect Signature" with some code that had been working perfectly > fine for the past month. I'd be happy to elaborate more, but just > shooting out this general inquiry in case if this is the wrong forum > for it. > > Thanks > > Bobby
[twitter-dev] Re: Has replies/mentions behavior changed again or it is broken?
I've had a few people reporting this problem to us too. On Aug 28, 12:28 am, "dean.j.robinson" wrote: > Just checking out my @ mentions and noticed there are a whole bunch > missing, took a little while to register what was going on, but it > looks like only tweet that begin with @username are being returned - > this is happening both on twitter.com and via the API. > > Anyone else notice this, and is it a bug or a feature...
[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] Language code in search query parameter.
Hello, Is it possible to use the language parameter as part of the "q" parameter in a search? Im thinging something along: "/search? q=ombudsman%20lang:se". This would let users save searches in their various clients, without the clients having support for the specific langage parameter. Thanks, Richard
[twitter-dev] Re: Basic Twitter / OAuth questions (.NET)
Many thanks for that - I've now got it working as intended. (I was, in fact, completely misunderstanding which tokens were which!) Much appreciated. :-) All the best, Rich. On Fri, May 1, 2009 at 3:45 PM, jmathai wrote: > > To get the access token you need to call /oauth/access_token. That'll > give you back tokens you can save and reuse. This is a good flow > diagram: http://oauth.net/core/diagram.png > > On May 1, 4:46 am, Richard L wrote: >> Hi, >> >> I've looked through the FAQ, archives and other websites, and haven't >> found anything that has helped on this, so apologies if I've just >> missed it! >> >> I'm building an application which needs to be able to set a user's >> status automatically, without that user needing to log in and approve >> it every time. >> >> I'm using a variation on the code >> at:http://www.voiceoftech.com/swhitley/?p=681 >> , and it's working - to an extent. >> >> A user can visit a page on my apphttp://www.mytwitterapp.com/twitter.aspx, >> be redirected to Twitter to approve the app, then be sent back to my >> app, to the page which now has the >> form:http://www.mytwitterapp.com/twitter.aspx?oauth_token=EQ8Mi7T2Xqi6y5Ka... >> >> I can then use that token to get the token secret and interact with >> Twitter (primarily setting a status update). >> >> However, if I try to use that token again, I get a "(401) >> Unauthorized" error. >> >> I thought that the oauth_token that gets returned >> fromhttp://twitter.com/oauth/authorizewas a token that I could store, and >> use to repeatedly access Twitter when needed. It seems that what I'm >> actually getting back is an Access Token. So, my questions are: >> 1. Does what I've written above make sense? >> 2. Is there a token I can store, and use to repeatedly access Twitter >> - and if so, how can I get that value? >> 3. Am I barking up the wrong tree entirely? >> 4. Anything else you think might be of help!! >> >> Many thanks in advance, >> >> Richard. >
[twitter-dev] Re: OAuth and Classic ASP
Hi Robert, I'm also looking into this once I get my .NET version problems sorted out - will let you know how I get on! All the best, Richard. On May 1, 4:36 pm, Robert wrote: > I am looking for some example code that I can use with a Classic ASP > legacy app. > > I am looking for a way to use oAuth with Classic ASP. > > Any help would be appreciated. > > Thanks in advance.
[twitter-dev] Basic Twitter / OAuth questions (.NET)
Hi, I've looked through the FAQ, archives and other websites, and haven't found anything that has helped on this, so apologies if I've just missed it! I'm building an application which needs to be able to set a user's status automatically, without that user needing to log in and approve it every time. I'm using a variation on the code at: http://www.voiceoftech.com/swhitley/?p=681 , and it's working - to an extent. A user can visit a page on my app http://www.mytwitterapp.com/twitter.aspx, be redirected to Twitter to approve the app, then be sent back to my app, to the page which now has the form: http://www.mytwitterapp.com/twitter.aspx?oauth_token=EQ8Mi7T2Xqi6y5Ka0d38AyyTG6dL7hFO5wdf2Bp9IDI I can then use that token to get the token secret and interact with Twitter (primarily setting a status update). However, if I try to use that token again, I get a "(401) Unauthorized" error. I thought that the oauth_token that gets returned from http://twitter.com/oauth/authorize was a token that I could store, and use to repeatedly access Twitter when needed. It seems that what I'm actually getting back is an Access Token. So, my questions are: 1. Does what I've written above make sense? 2. Is there a token I can store, and use to repeatedly access Twitter - and if so, how can I get that value? 3. Am I barking up the wrong tree entirely? 4. Anything else you think might be of help!! Many thanks in advance, Richard.
[twitter-dev] How do I acquire the twitter data mining feeds
I read the FAQ part in Twitter API site, and filled the form. But it seems it doesn't work. I still get 20 results per request. Can anyone tell me how to get the data mining feeds?
