Twitturly does too. Contact us for access though since it isn't
available to the public yet.
On Apr 8, 9:03 pm, Doug Williams d...@twitter.com wrote:
The API does not have a method to retrieve the information for a URLs.
tweetmeme offers an API [1] to discover URL information.
Hi Nick,
Yes, we can help with this. We have an API that is nearly complete
that will allow you to provide a URL and get all of the tweets that
contained a link to the provided URL, regardless of which URL
shortener that was used.
-Joel
On Apr 5, 12:02 pm, Nick Arnett nick.arn...@gmail.com
Ronnie, I'm showing that even #2 is different at times - what the user sees
on the Web UI at times will be different than both counts. It's all very
strange.
@Jesse
On Wed, Apr 8, 2009 at 9:54 PM, Ronnie ronniel...@gmail.com wrote:
There seemed to be a discrepancy in the follower count for
Hi Doug,
We are launching a new version later today which will also include
further data, most importantly we will include media for every link
(if it has any media)
so for instance if it is a blog post and it contains an image, we will
return a thumb_nail of that image that can be then used in
When I discovered that Twitter used the name from my recetly created
app via OAuth, I was pleased.
While the turn-around time for manual approval was great, I think that
using the data which we've already supplied through the creation of a
new OAuth app is the right way to go.
Keep up the good
I am interested in using OAuth for my twitter app but I have some
questions:
1. When twitter authorizes the user and returns the access tokens I
can store those tokens in my database for that user. Is it safe to say
those tokens will never change unless they were to re-authorize
themselves for
Why are you deprecating a very important feature for the basic auth method
while your OAuth support is still in beta?
The last official statement I read about Twitter and OAuth was that it went
public, but is still considered beta. Also, if I did not miss an
announcement, you were not yet
On Thu, Apr 9, 2009 at 04:19, Jas emailf...@gmail.com wrote:
I am interested in using OAuth for my twitter app but I have some
questions:
1. When twitter authorizes the user and returns the access tokens I
can store those tokens in my database for that user. Is it safe to say
those tokens
I recognize an odd behavior for the following property of embedded user
object in the friends timeline (XML format). As I understand from the API
docs, following should indicate whether the authenticating user is
following the returned user.
Obviously, all tweets returned on the
Hi.
I'm using java to develop a Twitter application.
I have the name of a user but I can't retry his7her screen name or
ID...
Can I do it?I search on google but I didn't find the solution.
Thanks.
Woke up this AM and went to check on a few things on our site... found that
all of the oAuth keys had been de-authorized that we had saved in our
database.
When I went to re-authorize, I got this error:
Woah there!
This page is no longer valid. It looks like someone already used the token
Andrew, please, less noise and more info. You are getting really
annoying lately.
Noorani, the source parameter is a code, which you had to request. I'm
saying had 'cause, as a few hours ago, Twitter decided to remove the
request form for new applications using the Basic Auth. See
Actually Julio what's really annoying are lazy eternal September people who
can't be bothered to read the FAQ and docs on their own, and those who
facilitate them by handholding and spoonfeeding.
On Thu, Apr 9, 2009 at 9:58 AM, Julio Biason julio.bia...@gmail.com wrote:
Andrew, please, less
I too am having problems with OAuth.
All of my keys have been de-authorized and I can't seem to re
authenticate as well.
On Apr 9, 8:36 am, Jason Korkin jkor...@gmail.com wrote:
Woke up this AM and went to check on a few things on our site... found that
all of the oAuth keys had been
It doesn't give you the right to be obnoxious. If you don't want to
answer, don't answer. Adding noise to the list won't help anyone.
On Fri, Apr 10, 2009 at 12:00 AM, Andrew Badera and...@badera.us wrote:
Actually Julio what's really annoying are lazy eternal September people who
can't be
Actually you can still request a source parameter for a few more days.
On Thu, Apr 9, 2009 at 08:58, Julio Biason julio.bia...@gmail.com wrote:
Andrew, please, less noise and more info. You are getting really
annoying lately.
Noorani, the source parameter is a code, which you had to
I just went through the authentication flow with http://twitter.abrah.am and
it worked fine.
On Thu, Apr 9, 2009 at 09:11, Adam coolbeansdud...@gmail.com wrote:
I too am having problems with OAuth.
All of my keys have been de-authorized and I can't seem to re
authenticate as well.
On Apr
Teach a man to fish...
-Stuart
--
http://stut.net/projects/twitter/
2009/4/9 Julio Biason julio.bia...@gmail.com:
It doesn't give you the right to be obnoxious. If you don't want to
answer, don't answer. Adding noise to the list won't help anyone.
On Fri, Apr 10, 2009 at 12:00 AM,
And how much noise are you adding now? If you feel like continuing your
uninvited preaching, feel free to take it up with me privately.
On Thu, Apr 9, 2009 at 10:12 AM, Julio Biason julio.bia...@gmail.comwrote:
It doesn't give you the right to be obnoxious. If you don't want to
answer, don't
Amen to that.
On Thu, Apr 9, 2009 at 10:16 AM, Stuart stut...@gmail.com wrote:
Teach a man to fish...
-Stuart
--
http://stut.net/projects/twitter/
2009/4/9 Julio Biason julio.bia...@gmail.com:
It doesn't give you the right to be obnoxious. If you don't want to
answer, don't
I too noticed some funky stuff this morning, but the authentication
flow worked fine for me.
What I did notice is that the verify_credentials.xml request is now
forcing the use of GET (I had been using POST up until now).
Are you certain that you are not re-using the same AccessToken? If you
Give a man a match, he'll have fire for a moment. Set a man on fire,
he'll burn the rest of his life.
;-D
On 4/9/09 10:16 AM, Stuart wrote:
Teach a man to fish...
-Stuart
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network |
Hi all,
Sorry for the late email but the deploys yesterday ran late and
we didn't get a chance to compile the change log. And a doozy of a
change log it is with 10 entries. Other things were deployed as well
but here are the 10 API-facing changes:
* Changed (REST): The since
Hi Greg,
The email parameter was deprecated [1] a little while ago with a
lot of ensuing discussion [2]. There is an open API issue on the
subject of re-adding some comparable feature [3]. When this feature
was deprecated you would have started getting back data for a user
name show
Please search the list archives. This functionality was depreciated
and announced on this list when it happened.
-Chad
On Thu, Apr 9, 2009 at 11:09 AM, greg schoen greg.sch...@gmail.com wrote:
I'm working on an issue with my app that appears to be emergent very
recently... evidently I am no
I was expecting that there would have been a note in the REST API
changelog, that's why I was a bit freaked out. Looks like this has
just been added to the changelog.
Thanks all
-Greg
On Apr 9, 10:25 am, Chad Etzel jazzyc...@gmail.com wrote:
Please search the list archives. This functionality
Thank you very much with the reply Julio.
and Mr. Andrew Badera! Please keep in mind that If you don't know any
thing or if you don't want to tell any thing then don't say
Impossible, just keep your mouth shut!!!
Thanks
On Apr 9, 6:58 pm, Julio Biason julio.bia...@gmail.com wrote:
Andrew,
LoL...
Mr. Andy Badera! It seems you have never used TweetDeck or Seesmic or
PeopleBrowsr or FriendFeed or TwitterFox that's why you've said like
that. Please if you don't know any thing then don't term it as
impossible.
Is any there anyone else who can guide me?
On Apr 9, 6:50 pm, Andrew
Thank you Doug for the reply.
Currently, I am able to get only about 1000 tweets from a user's
timeline, though the limit says about 3000. I also requested for the
whitelisting and am glad that it is accepted, but i don't know where
do i request for a datamining feed ?
Caching is something i
Yeah quite certain we're not re-using the same token. We're using GET
request.
On Thu, Apr 9, 2009 at 10:30 AM, Mobasoft mobat...@gmail.com wrote:
I too noticed some funky stuff this morning, but the authentication
flow worked fine for me.
What I did notice is that the
is this issue dead? I've been thinking about it - comments... anyone?
1) Not auto-rewriting URLs on input leaves the system susceptible to
various gregarious manipulation. It's currently trivial to get 10,000
visitors a day to click out of twitter and potentially up to 100,000 a
day - fictional
Wow, you really are quite clueless, aren't you? Feel free to reply when you
actually understand my words. In the meantime, try occupying yourself
educationally by reading the FAQ and API docs before asking any more silly
questions on this list, creating more noise.
On Thu, Apr 9, 2009 at 10:02
I got mu friends timelines btoken today because you changed from POST to
get, now I aligned properly.
Would be nice from you tellling this changes in advance. Areyou doing
release management?
Best regards,, Carlos
On Thu, Apr 9, 2009 at 12:20 PM, Matt Sanford m...@twitter.com wrote:
Hi all,
On Thu, Apr 9, 2009 at 7:13 AM, kanny fruhl...@coolgoose.com wrote:
Caching is something i will definitely be doing, but as i said, to do
something complex like semantic model generation, i need access to a
user's last, at least 100,000 friends_timeline tweets. For a typical
user following
@Carlos:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/85c582baac05694b/f20b1b4f6b42207c?#f20b1b4f6b42207c
On Thu, Apr 9, 2009 at 11:14, Carlos Crosetti carlos.crose...@gmail.comwrote:
I got mu friends timelines btoken today because you changed from POST to
get,
Carlos,
We're going to discuss today how we can better notify the community of
changes with due warning. After the Twitter API team meets today, I'll open
a thread here to discuss.
Regards,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 9:14 AM, Carlos
Same here. Moved to go the GET method for requesting.
Certain we are not re-using the same token.
Still having problems ...
On Apr 9, 9:42 am, Jason Korkin jkor...@gmail.com wrote:
Yeah quite certain we're not re-using the same token. We're using GET
request.
On Thu, Apr 9, 2009 at
Seems like a lot of people are on gmail here. I think a google alert would
work nice, that way we could get a stand out email.
On Thu, Apr 9, 2009 at 9:14 AM, Carlos Crosetti
carlos.crose...@gmail.comwrote:
I got mu friends timelines btoken today because you changed from POST to
get, now I
Come on guys, simmer down. I completely agree with the teach a man to fish
philosophy. If you see someone new, direct them to resources to help
themselves. Sometimes it is hand-holding that is appropriate, other times
it's teaching.
To the original question, we are shortly deprecating the ability
Does the consumer key/secret you are using still match what is on:
https://twitter.com/oauth_clients?
On Thu, Apr 9, 2009 at 11:30, Adam coolbeansdud...@gmail.com wrote:
Same here. Moved to go the GET method for requesting.
Certain we are not re-using the same token.
Still having problems
On Thu, Apr 9, 2009 at 12:42 PM, Doug Williams d...@twitter.com wrote:
If you already have a source parameter, you pass the parameter name as the
value of the HTTP header parameter 'source'.
To be pedantic, it should be sent as a POST variable named 'source',
not a true HTTP header value.
Nick,
That should allow clients an easier path to richly display tweets and linked
media. I'll be sure to look for the release.
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 4:15 AM, Nick Halstead nickhalst...@gmail.comwrote:
Hi Doug,
We are
Hi all,
I have yet to be able to reproduce this but that does not mean
there is no error. One thing that changed yesterday is the addition of
the Woah there page. That used to be a very ugly plain text 503 page
that said something like invalid / unauthorized token … we just made
it
Chad,
You're correct. I've yet to finish my full 16oz of coffee.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 9:54 AM, Chad Etzel jazzyc...@gmail.com wrote:
On Thu, Apr 9, 2009 at 12:42 PM, Doug Williams d...@twitter.com wrote:
If you already have a
Hi all,
I totally forgot to mention another feature I added yesterday.
The redirect back to your app after authorization now has two new
parameters. I added the user_id and screen_name so you can get to work
without calling verify_credentials.
Thanks;
— Matt Sanford
Yes, on my end it does.
On Thu, Apr 9, 2009 at 12:45 PM, Abraham Williams 4bra...@gmail.com wrote:
Does the consumer key/secret you are using still match what is on:
https://twitter.com/oauth_clients?
On Thu, Apr 9, 2009 at 11:30, Adam coolbeansdud...@gmail.com wrote:
Same here. Moved
On a personal note, even though I have created a few toy apps that
use OAuth to get a feel for it, I am holding off integrating OAuth
into several of my longstanding apps until the last possible minute
b/c of the current Beta instabilities (tho few, they still exist), and
the recent twitter
Hi Matt,
Unfortunately I don't have time right now to throw together a sample
app to test this, so I'll ask you :)
Do these new parameters play nice with possibly pre-existing
parameters in the callback?
i.e.
if callback is
http://foo.com/bar/baz.html
then the re-direct will actually call
Hi Chad,
They should, yes. I did not test what will happen if you already
have a user_id or screen_name parameter but based on the logic it
should add a second one. For an example of what they look like where
there are no other parameters take a gander at the return page on
Abraham's
If you include user_id or screen_name in you authorize url they will be
replaced on callback.
On Thu, Apr 9, 2009 at 12:27, Matt Sanford m...@twitter.com wrote:
Hi Chad,
They should, yes. I did not test what will happen if you already have a
user_id or screen_name parameter but based on
Hi all,
Just for some public closure on the issue Jason and I found the
issue. It was related to some POST/GET changes that were needed to
make everything work.
Thanks;
— Matt
On Apr 9, 2009, at 09:47 AM, Jason Korkin wrote:
Yes, on my end it does.
On Thu, Apr 9, 2009 at 12:45
Any reason why not? Just curious. Nice API by the way :)
Thanks,
Jamie
On Apr 9, 12:47 am, John Adams j...@twitter.com wrote:
On Apr 8, 2009, at 10:33 PM, orange80 wrote:
Yeah, I started checking the headers and realized that. It doesn't
seem like there's any hard limit on simultaneous
Hello,
Is there a way to search by link on the status message? For instance,
I'd like to pull all statuses submitted by TweetDeck application.
thank you
Hi Dough,
I do have my source parameter registered, however when i do a post and
set the source parameter, it still displays as web
Ive tried various source parameters, and sometimes it translates to
some random URL on github.com !
advise please...
On Apr 9, 12:42 pm, Doug Williams
What is your source parameter?
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 11:15 AM, Natelloyd natell...@gmail.com wrote:
So, for someone who just got involved with this yesterday, who DID
read the FAQs, how does this affect perl Net::Twitter users? I'm
http://search.twitter.com/operators
On Thu, Apr 9, 2009 at 13:22, joop23 joo...@gmail.com wrote:
Hello,
Is there a way to search by link on the status message? For instance,
I'd like to pull all statuses submitted by TweetDeck application.
thank you
--
Abraham Williams | Hacker |
The search twitter source:tweetdeck [1] will return any tweet with
'twitter' from the source with parameter 'tweetdeck'. Add your appropriate
format to the URL and you're good to go!
1. http://search.twitter.com/search?q=twitter+source%3Atweetdeck
Doug Williams
Twitter API Support
It should be noted that you can't just search for a source alone, you
must pass in some sort of query with it. So you can't really get all
tweets from a particular source...
One interesting way to use the source data handed back by the search
API is to gauge market share for certain
Hi all,
As part of a recent Google Code issue [1] I found out there is an
encoding bug in the current server-side version of the OAuth gem we're
using which prevents posting statuses that contain accented
characters. To fix this I'll need to upgrade the server-side gem.
While this should
tweetSPY
On Apr 9, 2:34 pm, Doug Williams d...@twitter.com wrote:
What is your source parameter?
Doug Williams
Twitter API Supporthttp://twitter.com/dougw
On Thu, Apr 9, 2009 at 11:15 AM, Natelloyd natell...@gmail.com wrote:
So, for someone who just got involved with this yesterday, who
Reviving old thread:
Seeing duplicates again, and now have examples:
http://twitter.com/ryanashleyscott/status/1485237579
http://twitter.com/ryanashleyscott/status/1485239348
same exact content, as far as i can tell, posted back-to-back by the user.
...apparently TweetGrid is scary :)
-Chad
There's currently not a way to look up a Twitter user by their real
name via the API.
On Thu, Apr 9, 2009 at 05:19, Fux funa@gmail.com wrote:
Hi.
I'm using java to develop a Twitter application.
I have the name of a user but I can't retry his7her screen name or
ID...
Can I do it?I
Hello all,
I wanted to throw out, what I would consider a necessary use case for oAuth.
An App should be able to revoke User access.
In the app dashboard in the twitter console, an App should be able to create
a block list, which prevents a user from accessing the app in the future.
Reason
I think that's a great idea. Seconded.
-Original Message-
From: Peter Denton petermden...@gmail.com
Date: Thu, 9 Apr 2009 12:14:19
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] oAuth - App Revoke User Access
Hello all,
I wanted to throw out, what I would
On 4/9/09 3:14 PM, Peter Denton wrote:
An App should be able to revoke User access.
Sure, just store a boolean in your app with the OAuth token as to
whether they're allowed to use your app or not.
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer
Yeah, I'm hearing this from my users again as well. Looks to happen
with timeouts and retries, same as my first email.
http://twitter.com/josephcolon/status/1484146426
http://twitter.com/josephcolon/status/1484146432
plus a few more, some for that user and some for others.
I've increased
On Thu, Apr 9, 2009 at 12:01 PM, Chad Etzel jazzyc...@gmail.com wrote:
Reviving old thread:
Seeing duplicates again, and now have examples:
http://twitter.com/ryanashleyscott/status/1485237579
http://twitter.com/ryanashleyscott/status/1485239348
same exact content, as far as i can tell,
Right on, Chad.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 1:34 PM, Chad Etzel jazzyc...@gmail.com wrote:
I would guess that when you have millions of connection requests a day
coming into a few different servers, you don't want the connection to
stay
Thanks everybody (except Andrew) for the support. I finally got my
source parameter working.
Hi,
Jerusalem timezone's DST (Daylight Saving Time) has started 2 weeks
ago and should now be GMT+3:00 while it was GMT+2:00 before it's DST
has started.
Twitter's API still returns 7200 as it's UTC offset while it should
now be 10800 (GMT+3:00). Twitter's site seems to display correct dates
in
It appears to be the same situation for US related timezones as well
(in the Settings tab). I'm not sure if twitter changes the offsets
due to DST, but would be nice to find out officially...?
-Chad
On Thu, Apr 9, 2009 at 4:44 PM, Saggi Malachi sag...@gmail.com wrote:
Hi,
Jerusalem
In the spirit of Twitter, I can also be contacted at @fizz -
http://twitter.com/fizz :)
On Apr 9, 10:44 pm, Saggi Malachi sag...@gmail.com wrote:
Hi,
Jerusalem timezone's DST (Daylight Saving Time) has started 2 weeks
ago and should now be GMT+3:00 while it was GMT+2:00 before it's DST
has
IMHO, That is beyond the scope of OAuth.
Your app should contain/maintain the logic for who is allowed in or in
this case, kept out.
It is foreseeable that having an OAuth API call to revoke your
application from the user (on their behalf, if you had read/write
access) could be a good thing to
That's what I had in mind, just to clarify.
-Original Message-
From: Mobasoft mobat...@gmail.com
Date: Thu, 9 Apr 2009 14:11:18
To: Twitter Development Talktwitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: oAuth - App Revoke User Access
IMHO, That is beyond the
I agree, in general, however the only reason I brought it up as scope is so
that it could serve both apps and twitter. This method would produce for
twitter a bad-list in general. But thanks
On Thu, Apr 9, 2009 at 2:13 PM, Brian Gilham bgil...@gmail.com wrote:
That's what I had in mind, just to
Thanks Nick for your gesture. I will certainly be interested in trying
out your cached tweets, but its usefulness will be limited to those
who follow the cached tweets' authors.
About sharing, i don't intend to publish in journals or conferences as
i can't afford the costs, but will definitely
On Thu, Apr 9, 2009 at 2:04 PM, kanny fruhl...@coolgoose.com wrote:
... It could change the twitter
client game completely as we dive deeper into the meanings of the
tweets instead of the keyword based or author based groupings.
That's what TwURLed News is about, but using a much simpler
What was the problem/issue?
On Apr 9, 2:19 pm, K.A.Noorani khurramnoor...@gmail.com wrote:
Thanks everybody (except Andrew) for the support. I finally got my
source parameter working.
There's also the BackTweets API. http://backtweets.com/api
-Chris Thomson
On Thu, Apr 9, 2009 at 2:27 AM, jstrellner jstrell...@urltrends.com wrote:
Hi Nick,
Yes, we can help with this. We have an API that is nearly complete
that will allow you to provide a URL and get all of the tweets
Just seen someone else twittering @twitterapi with a similar issue...
I try to post:
http://twitter.com/direct_messages/new.xml?user=foo567text=Ticketmaster+UK%3A+16.00+%281779%29
and get back the following xml (removed a url). I am following this
user, if I try to direct message an account I'm
This is a bug and Matt is currently working on the fix.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 3:04 PM, Pauly paulypo...@gmail.com wrote:
Just seen someone else twittering @twitterapi with a similar issue...
I try to post:
Hi Pauly,
Working on the issue now.
— Matt
On Apr 9, 2009, at 03:04 PM, Pauly wrote:
Just seen someone else twittering @twitterapi with a similar issue...
I try to post:
http://twitter.com/direct_messages/new.xml?user=foo567text=Ticketmaster+UK%3A+16.00+%281779%29
and get back the
(Please let me know if this has been discussed already. I searched for
“proxy” and didn’t quickly find anything related.)
At different times I like to have different “filters” on my tweet
viewing. When I’m in the office I can tolerate a large flow but when
I’m on a mobile device I want a subset
Dave,
This is certainly an idea that has been thrown around in conversation, but
there is no current development bandwidth to accomplish the task.
Hopefully this post can get some attention with the developers on the
boards. Are there any coders interested in working together to get a
prototype
Hi all,
The fix for this was just deployed. I'm updating the change log
now and will send the standard announcement email.
Thanks;
— Matt
On Apr 9, 2009, at 03:46 PM, Doug Williams wrote:
This is a bug and Matt is currently working on the fix.
Doug Williams
Twitter API Support
Hi all,
Hot on the heels of yesterday's mega-deploy we've put out two
small bug fixes for today, 2009-04-09:
* Fixed (OAuth): Accented characters in statuses were causing
signature error for OAuth clients. This has been corrected.
» See:
Hi Matt
I am still unable to access my connections tab to revoke priveldges
and re-test, but the first part was working great.
Thanks
Peter
Sent from my iPhone
On Apr 9, 2009, at 5:32 PM, Matt Sanford m...@twitter.com wrote:
Hi all,
The fix for this was just deployed. I'm updating
http://twitter.com/direct_messages/new.json?user=qinqi7text=test
I got The remote server returned an error: (400) Bad Request. Anything
wrong with this API invocation?
Thanks
--
Gary
http://twitter.com/garyzhao
... they appear to have changed the call from a POST to a GET.
I didn't see an update/change about this.
So, in PHP use:
$to = new TwitterOAuth($consumer_key, $consumer_secret,
$twitterOAuthToken, $twitterOAuthSecret);
$content = $to-OAuthRequest('https://twitter.com/account/
Especially with regards to the deprecation of certain things. I
totally missed the topic about the deprecation of the since param
which was only posted on the 8th. Reading it now it said:
Please use the next few days to update your application to use the
since_id
parameter if it is currently
Yeah, I was just wondering though if all the overhead of setting up
and tearing down connections for each request makes sense when a
client might need to download hundreds of statuses (to be stored in
local cache) the first time someone uses it.
On Apr 9, 3:34 pm, Chad Etzel jazzyc...@gmail.com
Anyone else has the problem that posting a status update through OAuth
gives the error: failed to validate oauth signatre or token since a
few hours?
I can't get RequestToken now, but my app is work yesterday :(
On Apr 10, 8:35 am, Matt Sanford m...@twitter.com wrote:
Hi all,
Hot on the heels of yesterday's mega-deploy we've put out two
small bug fixes for today, 2009-04-09:
* Fixed (OAuth): Accented characters in statuses
Try a GET instead of a POST.
On Thu, Apr 9, 2009 at 19:41, Chen Jie chenyue...@gmail.com wrote:
I can't get RequestToken now, but my app is work yesterday :(
On Apr 10, 8:35 am, Matt Sanford m...@twitter.com wrote:
Hi all,
Hot on the heels of yesterday's mega-deploy we've put out
I got the error on every requests by OAuth, just works fine
yesterday..
On Apr 10, 10:27 am, HSL hslee...@gmail.com wrote:
Anyone else has the problem that posting a status update through OAuth
gives the error: failed to validate oauth signatre or token since a
few hours?
400 is the response code we return for rate limiting. Are you sure
you're making the request using an HTTP POST? What was the body of the
response?
On Thu, Apr 9, 2009 at 18:22, Gary Zhao garyz...@gmail.com wrote:
http://twitter.com/direct_messages/new.json?user=qinqi7text=test
I got The
Apologies, Dean. We're going to formalize our API release scheduling
so this doesn't happen in the future.
On Thu, Apr 9, 2009 at 19:01, dean.j.robinson dean.j.robin...@gmail.com wrote:
Especially with regards to the deprecation of certain things. I
totally missed the topic about the
97 matches
Mail list logo
