[twitter-dev] Is gardenhose being ramped up?
I just took a look at my bandwidth usage from last night to see the effect of the VMAs (dramatic BTW), and thought I'd check it out over the last week. It looks like gardenhose has been ramping up since late Sept 10th/early Sept 11th. Is this intentional? Any idea where we're ending. My DB isn't keeping up with this so I need to reorganize if we're going to keep at this level. Help? Thoughts? http://twitpic.com/2o3ewf Sanjay -- 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: Is gardenhose being ramped up?
John - yeah, I saw the increase from that bump previously but if you look at the graph I included, this current bump is greater still. Mind you, I'm not complaining just trying to understand what is going on. If this increase is short lived I won't try to design around it. If it's going to be sustained, I want this data being sent down the pipe. Right now I'm seeing between 2k and 3k updates every 30 seconds whereas before a few days ago it was between 1k and 2k updates every 30 seconds. Any scoop would be helpful for planning purposes. Thanks! Sanjay On Sep 13, 12:05 pm, John Kalucki j...@twitter.com wrote: We increased the Gardenhose on August 30, as announced here:http://groups.google.com/group/twitter-api-announce/browse_thread/thr... . We haven't changed the proportion since. A Streaming API application should always be prepared for accept spikes of at least three, if not four times as large as daily peak traffic. -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Mon, Sep 13, 2010 at 8:43 AM, Sanjay sanjay.par...@gmail.com wrote: I just took a look at my bandwidth usage from last night to see the effect of the VMAs (dramatic BTW), and thought I'd check it out over the last week. It looks like gardenhose has been ramping up since late Sept 10th/early Sept 11th. Is this intentional? Any idea where we're ending. My DB isn't keeping up with this so I need to reorganize if we're going to keep at this level. Help? Thoughts? http://twitpic.com/2o3ewf Sanjay -- 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 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: A feed greater equivalent to the old gardenhose?
This is kind of a bummer. I just recently started using the gardenhose feed so comparing what is now available to what was available at gardenhose launch really doesn't satisfy me (and I suspect others). I started to build around the 6-8k/minute stream and this reduction to 2k/minute is definitely a hamper. I suppose it's just another challenge to develop around and I totally see your guys issue with consuming a load of bandwidth as you stream this data to developers without any compensation (as a side note, it'd be awesome to see graphs of incoming and outgoing bandwidth utilization at Twitter split up into pieces [streams, API, updates, etc.] - but then that may be competitive info you don't want to share). But with that, it would have been nice to have gotten a little heads up about the impending reduction rather than an explanation after the fact. I know there are a lot of moving parts over there but as with everything else Twitter does that impacts developers, a little notice about changes would help all of us adapt more effectively to the changing availability of data and connections. Regardless, thanks for the effort and dialog. If you guys are just being held up by not having a new name for the feed, may I propose renaming spritzer to drinking-straw and gardenhose to spray-faucet. Then you can use spritzer for the next level and gardenhose for the level just under firehose. That's one problem solved. :-) Sanjay
[twitter-dev] finding the number of accounts blocking a particular account
I know there was a post a while back about exposing which accounts may be blocking a particular account and using that info for retaliatory purposes but is there a way to get the sheer number of accounts blocking a particular account? This data point could be useful in knowing how to sort out actual accounts and marginal (but not yet banned) accounts. With a quick look I didn't find anything but maybe I missed something new or otherwise. Anyone know? Sanjay
[twitter-dev] A feed greater equivalent to the old gardenhose?
Just saw the posting about the reduction in the gardenhose (and sprtizer) feeds ( http://t.co/d6o1npx ). So for those of us who need the additional data and are designed around it (and can consume it), is there a way to get that level of feed back? For me in particular this is going to significantly hamper the app that I'm working on and was looking to launch in a few weeks. Help...? Sanjay
[twitter-dev] Gardenhose feed down to a trickle
I haven't fully investigated but my connection to the gardenhose feed has slowed to a trickle as of midnight EST last night. Looks like I'm seeing 1k updates/minute instead of the normal 3k-4k updates/minute. Just me or is this a known issue? I couldn't find any mention of it anywhere. Sanjay
[twitter-dev] Re: Desktop App oAuth GET request with valid accesstoken returns 401 Unauthorized
We are still trying with no luck :-(. Is somebody from Twitter
listening who could help us here? I think we are making some little
mistake which is blocking us. It's really frustrating. Maybe if
somebody could check at server side and let us know if our encoding or
string formation or what might be the issue. Please help!!! Does
it matter from which region (country) we are trying to make these
calls? I hope not. We are trying this from India.
Some more things we tried:
1. We put Authorization in header as below (once with oauth_signature
encoded and once without encoded, we get two different error codes,
see below for detail):
-Header without oauth_signature encoded
{User-Agent: Testweet
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth realm=Twitter API,oauth_consumer_key=---
removed---,oauth_nonce=68f3e3ca5d7440e5bac6cbc08029d817,oauth_signature_method=HMAC-
SHA1,oauth_timestamp=1261129193,oauth_token=---
removed---,oauth_version=1.0,oauth_signature=uVAiNwVqoSa8FFqZ/HRN/
rwhod0=
}
We get following error:
{Status: 500 Internal Server Error
Vary: Accept-Encoding
Connection: close
Content-Length: 4684
Cache-Control: no-cache, max-age=300
Content-Type: text/html; charset=utf-8
Date: Fri, 18 Dec 2009 09:40:27 GMT
Expires: Fri, 18 Dec 2009 09:45:27 GMT
Set-Cookie: _twitter_sess=xxx; domain=.twitter.com; path=/
Server: hi
}
-Header with oauth_signature encoded
{User-Agent: TestTweet
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth realm=Twitter API,oauth_consumer_key=---
removed---,oauth_nonce=88b3f32da1fe46c7af8581f63e869c14,oauth_signature_method=HMAC-
SHA1,oauth_timestamp=1261129414,oauth_token=---
removed---,oauth_version=1.0,oauth_signature=h
%2FHxJ9zS0UWISrh4T2762u5paA0%3D
}
We get following error:
{Status: 401 Unauthorized
Vary: Accept-Encoding
Connection: close
Content-Length: 148
Cache-Control: no-cache, max-age=1800
Content-Type: application/xml;
charset=utf-8
Date: Fri, 18 Dec 2009 09:44:13 GMT
Expires: Fri, 18 Dec 2009 10:14:13 GMT
Set-Cookie: _twitter_sess=xxx; path=/
Server: hi
WWW-Authenticate: Basic realm=Twitter API
}
Thank
On Dec 15, 6:52 pm, Sanjay shosansha...@gmail.com wrote:
Any Idea out there? I tried following to no avail:
a. Did the entire process (starting from registering the app and
generating consumer key/secret to getting Access Token/secret. Works
fine till I get Access Token Secret
b. When I copy/paste complete URL in browser's address bar, it prompts
[twitter-dev] Some links are throwing DNS error - cannot find server
Is it at my end or others are also facing this? I am getting DNS error - cannot find server for following urls - http://apiwiki.twitter.com/, http://help.twitter.com/forums/31935/entries, http://help.twitter.com/forums/10713/entries. I can log in and see timeline meaning twitter is available but these links are giving errors. Status says there was an outage some 3 hours back. Is it because of this?
[twitter-dev] Re: Desktop App oAuth GET request with valid accesstoken returns 401 Unauthorized
Hey Duane, many thanks for your reply. We did consider the existing .NET libraries but due to some reasons we were to write our own code for basic functionalities. Secondly, with our existing code we completed the process of getting access token and secret key without much problem. I am wondering what could be the issue with our request for verify_credentials? Thanks Sanjay On Dec 18, 6:55 pm, Duane Roelands duane.roela...@gmail.com wrote: Sanjay, There are several really good .NET libraries that handle OAuth already. I would give TweetSharp a look to see if it meets your needs. You might also want to look at TwitterVB. http://tweetsharp.comhttp://twittervb.codeplex.com On Dec 18, 5:01 am, Sanjay shosansha...@gmail.com wrote:
[twitter-dev] Re: Desktop App oAuth GET request with valid accesstoken returns 401 Unauthorized
Any Idea out there? I tried following to no avail:
a. Did the entire process (starting from registering the app and
generating consumer key/secret to getting Access Token/secret. Works
fine till I get Access Token Secret
b. When I copy/paste complete URL in browser's address bar, it prompts
for credentials saying - The server twitter.com:80 at Twitter API
requires a username and password. Wondering if port 80 is the
problem? But I think oAuth documentation states this as default
behaviour and I see no documentation on twitter to provide Port number
in URL.
c. Ran my program with both scenarios – logged in and logged out from
the twitter account in a browser.
d. Tried with both “/verify_credentials.xml” and “/user_timeline.xml”
More notes about the application:
1. .net 3.5/C#
2. Desktop/Console application
3. Using http://oauth.googlecode.com/svn/code/csharp/OAuthBase.cs as
the base and extended it to suit desktop/PIN related bits.
4. Stored Access Token and Secret in a text file and copy/pasted in
code as a consts (just if this matters. I cross checked the
characters).
5. The Twitter account shows application in SettingConnection and
SettingConnection Browse. I do not think this could be an issue that
the account for both is same.
6. Pseudocode (to access protected resources)
a. Generate Signature, Request URL and parameter with URI,
consumer key, consumer secret, token key and token secret
b. Concatenate Request URL, Parameters and Signature to form final
URL
c. Create HttpWebRequest object with URL
d. Set HttpWebRequest object’s method to GET
e. Set ServicePoint.Expect100Continue to false
f. Set UserAgent
g. Timeout 2000
h. Get a new StreamReader from HttpWebRequest.GetResponse
().GetResponseStream
i. StreamReader.ReadToEnd (ERROR!)
7. Stack Trace
• at System.Net.HttpWebRequest.GetResponse()
• at
OAuthWalkthroughConsole.WebHelper1.WebResponseGet(HttpWebRequest
webRequest) in D:\Development\POC\TwitterPrototype
\ConsoleTest2\ConsoleTest2\Program.cs:line 193
• at OAuthWalkthroughConsole.WebHelper1.WebRequest(String method,
String url, String postData) in D:\Development\POC\TwitterPrototype
\ConsoleTest2\ConsoleTest2\Program.cs:line 168
• at OAuthWalkthroughConsole.Program.Main() in D:\Development\POC
\TwitterPrototype\ConsoleTest2\ConsoleTest2\Program.cs:line 40
• at System.AppDomain._nExecuteAssembly(Assembly assembly,
String[]
args)
• at System.AppDomain.ExecuteAssembly(String assemblyFile,
Evidence
assemblySecurity, String[] args)
• at
Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly
()
• at System.Threading.ThreadHelper.ThreadStart_Context(Object
state)
• at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
• at System.Threading.ThreadHelper.ThreadStart()
How I wish Twitter returned more detailed errors! I could not make
anything of “401 Unauthorized”. Is it wrong token/key or the encoding
or the parameters, what?
Does Twitter API still have issues giving access to PIN based Token/
Secret from desktop clients? But I see many people got access. Is the
behaviour (of getting access through desktop) consistent?
What is going wrong here?
On Dec 15, 4:48 am, Sanjay shosansha...@gmail.com wrote:
I got my desktop application registered on Twitter and successfully
got the PIN which I used to generate Token and Secret Key. I am
generating following signature for verify_credentials:
http://twitter.com/account/verify_credentials.xml?oauth_consumer_key=...
It always returns 401 Unaushorized error. Am I missing something. The
Response Header below:
Response Object Header
{Status: 401 Unauthorized
X-Runtime: 0.00163
Vary: Accept-Encoding
Connection: close
Content-Length: 419
Cache-Control: no-cache, max-age=1800
Content-Type: application/xml; charset=utf-8
Date: Mon, 14 Dec 2009 23:34:46 GMT
Expires: Tue, 15 Dec 2009 00:04:46 GMT
Set-Cookie:
_twitter_sess=BAh7BzoHaWQiJWZhYWE0ZjgwOTY4ZDA5ZDIzMjRjOTVmY2UxMmNlOWM1Igpm
%250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
%250AOgpAdXNlZHsA--482b347c66dc8e1643fcf1b99a82f36aeee38f41;
domain=.twitter.com; path=/
Server: hi
WWW-Authenticate: Basic realm=Twitter API
}
[twitter-dev] Desktop App oAuth GET request with valid accesstoken returns 401 Unauthorized
I got my desktop application registered on Twitter and successfully
got the PIN which I used to generate Token and Secret Key. I am
generating following signature for verify_credentials:
http://twitter.com/account/verify_credentials.xml?oauth_consumer_key=YvrptruncatedSAxFljgoauth_nonce=8334754oauth_signature_method=HMAC-SHA1oauth_timestamp=1260833274oauth_token=ASGgOe4Zvv7XB1YftruncatedmNyd0wse4ydEzR2Qoauth_version=1.0oauth_signature=HWtyOQ5SSJ4wARVoQI2sEy8PA5M=
It always returns 401 Unaushorized error. Am I missing something. The
Response Header below:
Response Object Header
{Status: 401 Unauthorized
X-Runtime: 0.00163
Vary: Accept-Encoding
Connection: close
Content-Length: 419
Cache-Control: no-cache, max-age=1800
Content-Type: application/xml; charset=utf-8
Date: Mon, 14 Dec 2009 23:34:46 GMT
Expires: Tue, 15 Dec 2009 00:04:46 GMT
Set-Cookie:
_twitter_sess=BAh7BzoHaWQiJWZhYWE0ZjgwOTY4ZDA5ZDIzMjRjOTVmY2UxMmNlOWM1Igpm
%250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
%250AOgpAdXNlZHsA--482b347c66dc8e1643fcf1b99a82f36aeee38f41;
domain=.twitter.com; path=/
Server: hi
WWW-Authenticate: Basic realm=Twitter API
}
[twitter-dev] Re: Public Timeline Frozen
I'm not entirely sure but this may be somewhat my fault. Yesterday I noticed two different tweets in the public timeline that were attached to protected accounts. I don't think they were an effect of the accounts going from public-private since I caught them right after they showed up and saw the accounts were protected. I emailed Twitter at 4:36pm and then another one at 5:16pm (EST). That *may* be the reason. That said, I'm glad I'm not the only one noticing that the public timeline was frozen. I thought I was crazy for a while yesterday and then started looking at other options (none of which have worked out that well). Sanjay
