7;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
ng. 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/
ust
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
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
significantly hamper the app that I'm working on and
was looking to launch in a few weeks.
Help...?
Sanjay
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
Hi Andy, just to update they are working now!
Thanks
Sanjay
On Dec 18, 6:45 pm, Andrew Badera wrote:
> DNS was attacked yesterday or last night. Issues are probably still
> ongoing/being sorted out.
>
> ∞ Andy Badera
> ∞ +1 518-641-1280 Google Voice
> ∞ This email is: [ ]
what could be the issue with our
request for verify_credentials?
Thanks
Sanjay
On Dec 18, 6:55 pm, Duane Roelands 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
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
e, 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 wrote:
> Any Idea out
es 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 wrote:
> I got my desktop application registered
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=YvrptruncatedSAxFljg&oauth_nonce=8334754&o
started looking at other options (none of which have worked out
that well).
Sanjay
13 matches
Mail list logo
