Hello,
I'm trying to get advice from other developers about a schema change
that is intermittent. I couldn't find any API announcements that cover
this and it makes error detection a bit of a pain.
This is what's happening:
A 401 Unauthorized, depending on the endpoint, has a completely
differen
at Twitter applications.
Our API has grown to include fluent and service-based support for 100%
of the Twitter API, and most recently Yammer as well.
We're going to do our best to make it to Chirp this year.
@dimebrain and @jdiller
On Feb 19, 3:20 pm, Abraham Williams <4bra...@gmail.com> wrote:
That's not the only ticket open on the subject.
Issues 1239 and 1229 exist, so did 1350.
And it's a big problem for my team, namely because we can't create and
then delete lists for our unit tests, and many people rely on our
library.
I hope this is resolved soon.
On Dec 30 2009, 10:12 am, Yusu
oice
> > ∞ This email is: [ ] bloggable [x] ask first [ ] private
> > ∞ Google me:http://www.google.com/search?q=andrew%20baderaOnThu, Dec 17,
> > 2009 at 7:05 AM, Dimebrain wrote:
> > > The following retweet methods have started returning 404's in our u
;>http://twitter.com/statuses/show/5211439124.xmldoes not return a 404
> >>http://api.twitter.com/1/statuses/retweets/5211439124.jsonreturns a
> >> 404
>
> >> So, obviously the status is there, but the retweet api isn't working;
> >> or maybe they have sta
t; ∞ +1 518-641-1280 Google Voice
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me:http://www.google.com/search?q=andrew%20badera
>
> On Thu, Dec 17, 2009 at 7:05 AM, Dimebrain wrote:
> > The following retweet methods have started returning 404's in our
The following retweet methods have started returning 404's in our unit
testes:
http://api.twitter.com/1/statuses/retweeted_by_me.json
http://api.twitter.com/1/statuses/retweeted_to_me.json
http://api.twitter.com/1/statuses/retweets_of_me.json
http://api.twitter.com/1/statuses/retweets/[any_status_
My colleague and I added Lists support to our C# Twitter Library
(tweetsharp.com) recently and during unit testing we created several
lists, expecting to destroy them with similar API calls during the
test. The DELETE calls returned successfully but the lists were never
deleted.
In fact, we can't
The current endpoint for creating a new list is:
http://api.twitter.com/1/user/lists.format
But the "user" part is meant to be the user's screen name.
If your application is oAuth, you don't necessarily know or care about
the user's screen name.
You can easily get it with a verify_credentials c
Hello,
Two things of note on the public timeline as of 12PM EST:
a) All profile photo URLs are returning as the default stock profile
photo, even if the user normally has one defined
b) The element returned in the public timeline is the classic
"short" representation, not the fully detailed re
Matt is right on the money here.
And if you are using .NET, you can avoid the challenge-response issue
by setting your Authorization header directly, rather than creating a
NetworkCredential instance. That's the only way to avoid the initial
two hits to the API before a handshake is established.
The reason why your code didn't work originally is because setting the
ServicePoint.Expect100Continue on the static method will set it to
false only for all HttpWebRequests created *after* you set it to
false. In this case you created your WebRequest prior to setting the
flag to false. If you move
How are you able to set this up for a non-standard port? HOSTS file is
just for the domain/authority, and you can't specify a port in the
callback URL on the settings page?
On Apr 23, 7:31 pm, Jochen Kaechelin wrote:
> Am 24.04.2009 um 00:29 schrieb Paul Kinlan:
>
> > Hi,
>
> > During developmen
I'm calling /direct_messages.xml and getting back this:
-
98485094
780830
-
Top secret DM of incalculable value.
11173402
Mon Apr 20 17:14:39 + 2009
BPAndrew
dimebrain
-
780830
Andrew M
BPAndrew
Ottawa
-
First Sea Lord Admiral Sir BPAndrew McHugeWangington III
-
http
not quite.
On Apr 17, 8:29 am, Dossy Shiobara wrote:
> On 4/16/09 10:56 PM, Dimebrain wrote:
>
> > It should be no different than if you persisted the access token
> > yourself and went to call the API a few weeks after doing so, you
> > should be able to trust that your
I just realized I don't know whether the remaining_hits element
returned for /account/rate_limit_status is a static number from the
beginning of the current hour, or if it is the remaining hits on a
rolling sixty minute cycle. Does anyone know?
Assuming that the authentication process is handing you off the actual
access token, it makes sense that it can't be exchanged. I don't think
the token will expire on you though, at least today, so you don't
really need any more verification other than maybe running account/
verify_credentials aga
Consider this code snippet who's task is to display the first page of
a user's tweets:
const double tweetsPerPage = 20;
string screenName = "Dimebrain";
double updatesCount = 821;
double pages = updatesCount / tweetsPerPage;
tatus=testing parameter should be in the body, like a
> normal x-www-form-urlencoded POST.
>
> Thanks;
> — Matt Sanford / @mzsanford
>
> [1] -http://code.google.com/p/twitter-api/issues/detail?id=433
>
> On Apr 14, 2009, at 09:28 AM, Dimebrain wrote:
>
>
>
&g
This behavior resolved as of this morning; no need to investigate
further, and no changes made.
On Apr 13, 1:31 pm, Dimebrain wrote:
> Hello,
>
> Recently, I have noticed that if I attempt to do a request token /
> access token exchange, i.e. a new application OAuth workflow, I a
Hello,
I originally commented on issue thread 447 but that issue was closed,
so I wanted to repost my problem to see if it's something I'm doing
wrong on my side.
I am still failing, but using C# / .NET and a self-authored OAuth
implementation.
My GET calls work correctly, my POST calls 401.
H
This query contains two documented search operators, and it bombs with
a 404 if they're called together, but works if called separately.
Previous unit tests allowed multiple operators. Is 404 the correct
response for "no results"? It returns as HTML.
http://search.twitter.com/search.json?q=twitte
Hello,
Recently, I have noticed that if I attempt to do a request token /
access token exchange, i.e. a new application OAuth workflow, I always
fail with "Failed to validate oauth signature and token" from Twitter
if the application has already been successfully authorized in a
previous workflow
ally repro the above situation)
> and report back.
>
> JD
>
> On Tue, Apr 7, 2009 at 11:29 AM, Dimebrain wrote:
>
> > Isn't request.PreAuthenticate = true functionally equivalent to adding
> > the credentials manually to avoid the double calls?
>
> > On Apr 5,
Isn't request.PreAuthenticate = true functionally equivalent to adding
the credentials manually to avoid the double calls?
On Apr 5, 1:21 am, James Deville wrote:
> Look at what requests you are sending with Netmon or Wireshark. With Witty
> (C# wpf app), we discovered that first an unauthentica
I actually ran this experiment already for a dating app concept, using
some established research on gender detection based on writing
(against at least 10-20 tweets) combined with a database of female
names for user names. I also tried running this on an ANN but that
wasn't fruitful and required m
I think you might be missing oauth_token from your access_token URL
parameter string in the snippet above, it should travel with the other
parameters and it its secret is hashed with the consumer secret in the
signature base.
It can be painful to solve whatever small deviation is causing your
pro
> The way I see it now (or at least in the recent past), this board has
> been mainly used for asking how to get a source parameter, basic
> how-to-get-started type questions, and reporting twitter service
> outages or glitches that the twitter team are probably already
> painfully aware of. I k
ave never been able to make a protected
> resource request there may be an error in your implementation.
>
> Dimebrain wrote:
> > Just out of curiousity are you supporting the Authorization header
> > form of OAuth when making protected resource requests? I know they
> > work
e experiencing
> a transient issues. If you have never been able to make a protected
> resource request there may be an error in your implementation.
>
> Dimebrain wrote:
> > Just out of curiousity are you supporting the Authorization header
> > form of OAuth when making protec
Mar 27, 2:20 am, Dimebrain wrote:
> I am able to consistently exchange the request token for the access
> token and see my application in the Connections tab for my account.
> However, I'm no longer able to make protected resource requests with
> the final token and secret. It work
I am able to consistently exchange the request token for the access
token and see my application in the Connections tab for my account.
However, I'm no longer able to make protected resource requests with
the final token and secret. It worked for me earlier in the evening,
but now is consistently
When I make a call to get a request token, the response contains, as
it should, an oauth_token_secret. What I don't understand is why I
can't actually use that oauth_token_secret in the signature hash
before trying to exchange it for an access_token; if I ignore that
token secret and hash with an
Definitely just me. As you were, Internet.
On Mar 25, 10:17 am, Dimebrain wrote:
> Running my usual unit tests, I seem to fail when any Basic Auth is
> used with "Could not authenticate you" returned for those requests.
> This is occurring for multiple accounts that lo
Running my usual unit tests, I seem to fail when any Basic Auth is
used with "Could not authenticate you" returned for those requests.
This is occurring for multiple accounts that log in correctly when
using the twitter.com web interface. I haven't made any changes to
this code in a long time and
Hi Matt,
Is there an issue # to track this? I'm definitely seeing intermittent
refusals for tokens with a different amount of waiting time each time,
at the request_token, access_token and protected resource stages. I
was just curious if this was still a live issue.
On Feb 23, 2:31 pm, Matt Sanf
I found my problem.
My Authentication header information had an erroneous extra comma.
This was allowed when requesting the token, but not when exchanging
for the authorized token.
Removing the comma results in proper access_token retrieval.
On Mar 18, 7:27 pm, Dimebrain wrote:
> He
That makes sense, .NET's HttpUtility.UrlEncode method doesn't encode
in uppercase hexadecimal, and the OAuth 1.0 spec requires that.
On Mar 19, 7:20 pm, Shannon Whitley wrote:
> It's working now. I changed the method for url encoding my post
> variables and that seemed to fix the problem. I'm
Hello,
I'm unit testing my OAuth implementation and am able to obtain a
request token successfully. After obtaining it, I redirect the user to
the authorize URL (with token parameter and no callback) and hang and
wait for a few seconds while I click "Allow" on the token's redirected
authorization
d), where as HttpWebRequest raises HttpWebException which you can
> directly check for a 503 error.
>
> Anyway, I really enjoy using Tweet# and if any .Net devs out there need a
> .Net Twitter library this is the one I recommend.
>
> Paul
>
> 2009/3/3 Dimebrain
> I understand), where as HttpWebRequest raises HttpWebException which you can
> directly check for a 503 error.
>
> Anyway, I really enjoy using Tweet# and if any .Net devs out there need a
> .Net Twitter library this is the one I recommend.
>
> Paul
>
> 2009/3/3 Dimebra
gards,
> Paul
>
> 2009/3/3 Dimebrain
>
>
>
> > I have experienced sending search requests out which return a plain
> > string, rather than JSON representing a twitter error. It's this:
>
> > "You have been rate limited. Enhance your calm."
>
> &
I have experienced sending search requests out which return a plain
string, rather than JSON representing a twitter error. It's this:
"You have been rate limited. Enhance your calm."
a) What is the rate limiting based on, IP or client? What is the
limit? I develop a Twitter library (tweetsharp)
I think there's some erroneous caching occurring with these optional
parameters for disambiguation when using JSON.
If I make this request:
http://twitter.com/users/show.json?screen_name=413
I get back the correct user whose screen name is 413 and whose id is
16089382.
If I then make this reque
Thanks for offering to collect this info, Alex.
Twitter Username: @dimebrain
URL: http://dimebrain.com
Email: i...@dimebrain.com
Technology: .NET, C#, Silverlight and WPF
On Feb 23, 2:33 pm, Alex Payne wrote:
> There isn't one that I'm aware of, but if people would like to post
&g
A few hours ago, my calls to get user's timeline have been returning
that I have exceeded my rate limit (I am whitelisted). Calls to
friend's timeline work as expected. Calls to my rate limit (auth'd)
report that I have in fact exceeded my 100 calls per hour (again, I'm
whitelisted).
Is anyone el
http://twitter.com/direct_messages.atom?since=Tue%2C+27+Mar+2007+22%3...
>
> --Eric
>
> On Jan 31, 2009, at 6:52 PM, Dimebrain wrote:
>
>
>
> > output of unit test (calling since with date prior twitter launch,
> > fails with closer dates as well)
>
> > wi
ce'
1 direct messages found with 'since'
On Jan 31, 4:27 pm, Alex Payne wrote:
> Sounds like we don't have direct messages for you since the date
> you're specifying :)
>
> On Sat, Jan 31, 2009 at 00:58, Dimebrain wrote:
>
> > I'
;t havedirectmessagesfor you since the date
> you're specifying :)
>
> On Sat, Jan 31, 2009 at 00:58, Dimebrain wrote:
>
> > I'm not able to make a call to getdirectmessagessent or received by
> > the authenticating user if I add the "since" parameter, p
we don't have direct messages for you since the date
> you're specifying :)
>
> On Sat, Jan 31, 2009 at 00:58, Dimebrain wrote:
>
> > I'm not able to make a call to get direct messages sent or received by
> > the authenticating user if I add the "since&
I'm not able to make a call to get direct messages sent or received by
the authenticating user if I add the "since" parameter, passing the
correctly formatted / url-encoded date. All I get back is "nil".
Even with the demo API call in the REST documentation, i.e.:
http://twitter.com/direct_messag
wrote:
> Is it possible that you're attempting to log into Twitter with bad
> credentials? When go back to the Twitter web site are prompted to
> solve a CAPTCHA or told that your account is temporarily locked?
>
>
>
> On Wed, Jan 21, 2009 at 17:58, Dimebrain wrote:
>
&
e a CAPTCHA or told that your account is temporarily locked?
>
>
>
> On Wed, Jan 21, 2009 at 17:58, Dimebrain wrote:
>
> > Currently, when I attempt the following API calls I receive the "rate
> > limit exceeded" error:
>
> >http://twitter.com/statuses
s uses Twitter besides me so I can't figure it
has to do with my IP address exceeding limits. Does anyone have any
ideas? Is it just erratic / erroneous messages returned?
@Dimebrain
The JSON date format for REST calls is:
Fri Dec 19 17:24:18 + 2008
But the JSON date format for Search calls is:
Tue, 13 Jan 2009 18:10:17 +
Is this a bug, or just something to account for?
The property is "created_at"
esn't need
auth, at least. But it seems less than useful in the grand scheme of
things.
On Jan 13, 3:33 pm, "Steve Brunton" wrote:
> On Tue, Jan 13, 2009 at 2:16 PM, Dimebrain wrote:
>
> > I was hoping to be able
> > to keep everything on the client-side; can you
ks like a charm.
Thanks!
On Jan 13, 3:33 pm, "Chad Etzel" wrote:
> On Tue, Jan 13, 2009 at 2:16 PM, Dimebrain wrote:
>
> > Yes, you nailed it. I want to insert a script tag to send the request,
> > and somehow attach auth info to it going out the door, and your answer
> &g
Yes, you nailed it. I want to insert a script tag to send the request,
and somehow attach auth info to it going out the door, and your answer
is what I feared but suspected; no, I can't do that. If I use a server
proxy I might as well just have a service that sends and receives
messages to and fro
I realize session auth isn't supported, but considering that JSONP
callbacks are, is it possible to avoid a prompt for username and
password when making requests w/ JSON callbacks that require them?
Since I'm basically just injecting javascript to make the request,
it's not obvious to me how to se
59 matches
Mail list logo
