See guys, there you go again.
The Trending Topics is no longer in the sidebar, there's nothing on
the Twitter Status blog about it.
Do a search for Trending and you'll notice that we are all wondering
what's going on.
Do we need to have a refresher course in Transparency 101 ?
What gives?
Hi there,
Can you provide some sample URLs giving you trouble so I know
where to look?
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Apr 29, 2009, at 8:35 PM, rleber wrote:
I am getting frequent 500 errors when using the search api. This began
at about 7pm Eastern today.
Hi there,
It looks like there was a problem with that portion of the site
causing 500s for everyone with the new sidebar (a small percentage or
users). To let those people at least use the site the feature was
disabled until it can be fixed. That seem reasonable but I'm not sure
why
Hi there,
The most common cause of X-RateLimit-Remaining not matching a
call to rate_limit_status is that you're not authenticated when
calling rate_limit_status but you are when making the call with the
different header. This is usually caused by libraries that require a
401
Getting the same problem for /status/followers.json
Request for /verify/credentials.json works but not for /status/
followers.json
verify credentials header:
GET /account/verify_credentials.json?
Hi,
I would like to develop some kind of mashup by categorizing a few twitter
profiles(the idea would be something like
http://tweetminster.co.uk/mps/party/LD)
the problem is that I'm not sure how to focus it without hammering the
twitter api servers. the first idea was just to perform a search
We're checking by two ways:
Manually through the web
Through the friends and followers lists of the REST API (The new
friends do not exist)
We wonder if it might be a problem only with https requests and XML
format or if others have this problem with http, JSON, and so on.
We checked
Never mind -- I found the problem. (Undocumented change to behavior of
Ruby twitter gem...)
Sorry for wasting anybody's time :-)
rl
On Apr 29, 11:35 pm, rleber richard.le...@gmail.com wrote:
I am getting frequent 500 errors when using the search api. This began
at about 7pm Eastern today.
Hi,
I am trying to use the twitter search api jsp file. can you tell me
how I can read the data from the atom result.
sravs..
Hello all,
Im am currently making a website that uses the twitter api. I am able
to obtain the background image of my twitter profile using the url
http://twitter.com/users/show.xml?screen_name=screen_name_here
Which returns something like this:
Hmmm. Very clever solution to use Google and I agree that unique
people MENTIONING a term is more valuable then the actual mention.
It's wild to me that the Twitter API has not started to incorporate
more stat related metrics. Seems crazy to me that a server as useful
as Twitter that has
We're trying to gather meaningful statistics about Twitter favorites,
which means we have to crawl a high number of profiles and, worse, a
high number of people's favorites' pages. The latter also has to be done
regularly to update the statistics.
Currently, the /favorites method only always
Just noticed that the followers count on my profile at twitter.com is
different from the count retrieved via the API. The JSON via the API
gives the correct count, while the website reflects a false count
triggered by someone who must have clicked follow twice, which was
also reflected by a
Received two more similar issues yesterday and one this morning at
10am. In all instances it was a GET request for either statuses/
friends or statuses/followers and the page parameter was always 1.
If you need any more info please let me know.
On Apr 29, 8:31 pm, Dossy Shiobara
friendships/exists.json
*not*
friendship/exists.json
On Tue, Apr 28, 2009 at 11:06, tayknight taykni...@gmail.com wrote:
I'm fairly sure I'm getting a proper token. Using the page
http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html I
get the same signature as in my failing url.
statuses/followers.json
*not*
status/followers.json
On Thu, Apr 30, 2009 at 01:47, app apphac...@gmail.com wrote:
Getting the same problem for /status/followers.json
Request for /verify/credentials.json works but not for /status/
followers.json
verify credentials header:
GET
Hi there,
That's really up to you, but probably something like the rome
library [1].
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1] - https://rome.dev.java.net/
On Apr 30, 2009, at 2:47 AM, sravs.. wrote:
Hi,
I am trying to use the twitter search api jsp file. can you
On Thu, Apr 30, 2009 at 04:31, CentralB-Dev developm...@central-b.comwrote:
We wonder if it might be a problem only with https requests and XML
format or if others have this problem with http, JSON, and so on.
You could easily test this yourself and know for sure.
We checked immediately,
If you are just pulling all this information from your own account's friends
timeline, how would you be hammering the twitter API? I can't imagine you'd
need to do that more than once a minute (tops!). That still leaves you with
40+ additional calls / hr you can make.
Cache all the data you get
Oh thanks Matt, but as you can see I have already removed snarky - I
though about it some more and figured that it wasn't any of my
business. You guys are doing a good job, I should keep the snarkiness
to a low roar, and only when needed.
Thanks for the information. By the way, I'm about ready
How big are the friend/follower sets? Are they large? Is there a user you
can consistently use to invoke this error?
Like I said, this is a difficult one to track do. Details and
reproducibility are helpful.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On
Sounds like stale caching data. It is a known shortcoming to the engineer
responsible for our core caching architecture.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Thu, Apr 30, 2009 at 7:51 AM, dozykraut bernhard.schul...@gmx.netwrote:
Just noticed
We would prefer large applications to cache and serve images locally to
offload our operation costs. However, for smaller applications and
development efforts, serving from the S3 URL provided with the API is
acceptable.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
Well, I feel like a moron. Thanks for the help. Sorry to have asked
you to spend time on something so ridiculously simple.
On Apr 30, 11:04 am, Abraham Williams 4bra...@gmail.com wrote:
friendships/exists.json
*not*
friendship/exists.json
On Tue, Apr 28, 2009 at 11:06, tayknight
the possible hammering could come when I select a certain category and then
I send a request to fetch the status for each account I have assigned to
this category...
regards
On Thu, Apr 30, 2009 at 6:24 PM, P Burrows pburr...@gmail.com wrote:
If you are just pulling all this information from
When the earlier developer posted, it wasn't possible to confirm that.
In the time sense then we've resolved the issue, and the problem was
with a faultily implemented method on our app's end.
Our use of GET versus POST on a POST-only API method, plus the
method's false positive interpretation
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
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.
I have noticed that this issue occurs for users that have friend/
follower sets greater than 1000. For instance the three cases I
mentioned in my previous post all had friend/follower sets in the
thousands. There could be exceptions and maybe Dossy Shiobara has come
across cases where the sets
Just got 3 truncated XML requests from the users below, all of whom
have friend/follower sets 1000. One thing to note about how my
application works. If the application is getting a user's friend/
follower set and if the first GET request fails for whatever reason,
the application retries 2
That is where caching comes into play. Fetch the data from Twitter once
every [n] minutes. Store it locally (in some database on your server). When
a request for a certain category comes, you pull it all out of your local
DB. User requests never wait for Twitter. Twitter never gets hammered.
Before today, the value of the in_reply_to_status_id field was validated by
two requirements,:
1) It was set to a valid status_id
2) The valid status_id's author from #1 was @replied in the update (@reply
here is the old definition where @user was at the beginning of the tweet).
If the value of
I just wanted to bring back attention to this. Has anyone on the list
gotten Twitter's OAuth to work with Perl? Care to share some code examples?
Thanks,
Jesse
On Wed, Apr 22, 2009 at 1:40 AM, Jesse Stay jesses...@gmail.com wrote:
Matt, here's what I'm getting back:
On Tue, Apr 21, 2009 at
On Thu, Apr 30, 2009 at 11:22 PM, Jesse Stay jesses...@gmail.com wrote:
I just wanted to bring back attention to this. Has anyone on the list
gotten Twitter's OAuth to work with Perl? Care to share some code examples?
I'm using Perl's Net::OAuth heavily, but only for updating twitter status
We're in the process of implementing twitter auth into a service that
already supports OpenID. As such, we are using a URL as the user
identifier, which is the standard idiom in the OpenID world. Since a
user can change their screen name, the twitter profile URL is not
reliable for use in
I happy to report that I have the new UI on my account and it's nice.
However, apparently the status param is no longer recognized.
http://twitter.com/home?status=thisusedtowork
That would put thisusedtowork in the What are you doing? box.
Now of course I'm probably reading this wrong, or
I'm just reading http://apiwiki.twitter.com/Streaming-API-Documentation#firehose
So is the firehose live?
I see that this is available only to approved parties, and requires a
signed agreement to access.
Are the approval guidelines/criteria and text of the agreement
available for review?
-Ken
Hi there,
We're working on getting that fix out right now. I was hoping we
would get the fix pushed out and I could just re-cap after the fact :)
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Apr 30, 2009, at 2:51 PM, Dave Winer wrote:
I happy to report that I have the new
The statuses/show method is perfect [1].
1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0show
Thanks,
Doug
Doug Williams | Platform Support | Twitter, Inc.
539 Bryant St. Suite 402, San Francisco, CA 94107
Currently it would require a URL to be constructed after getting the
username from users/show [1]. I will find out if there is interest in an ID
based redirect as have you suggested.
1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
Thanks,
Doug
--
Doug Williams
Twitter
On Apr 30, 2009, at 4:00 PM, Matt Sanford wrote:
Hi there,
We're working on getting that fix out right now. I was hoping we
would get the fix pushed out and I could just re-cap after the fact :)
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Apr 30, 2009, at 2:51 PM, Dave
Hello,
If I request a listing of friends should it include all people who I added as a
friend throughout time even though I may have un-followed them? That is what I
am seeing. Do I need to use the social graph Friend method to filter those out?
Jeff
Well, sure. But, I was thinking more of building a url ala:
http://twitter.com/demosthe/status/1659019581
--
Patrick Burrows
http://www.CleverHumans.com
On Thu, Apr 30, 2009 at 7:13 PM, Doug Williams d...@twitter.com wrote:
The statuses/show method is perfect [1].
1.
Hi all,
We added two new features today (2009-04-30) based on the
feedback we've been getting:
• Feature (REST): The in_reply_to_status_id can now reference any
mentioned user.
» See Also: Announcement at http://bit.ly/kFDTl
• Feature (REST): The social graph methods
I was suggesting using the call to statuses/show to build this URL
programmatically, like with this psuedo-code:
$status = new Status( http://twitter.com/statuses/show/; +
$in_reply_to_status_id+ .xml)
$screen_name = $status-get_screen_name();
echo http://twitter.com/; + $screen_name + /status/
Iam is the biginner and iamnot fluent in english language, so iam very
sorry for this, iahope to some one to help me tobe number one thansk
full
2009/4/30, rleber richard.le...@gmail.com:
Never mind -- I found the problem. (Undocumented change to behavior of
Ruby twitter gem...)
Sorry for
No. It should not. If you recently stopped following them it might take a
little while for the cache to clear.
On Thu, Apr 30, 2009 at 18:43, Jeff Bishop jeff.bis...@gmail.com wrote:
Hello,
If I request a listing of friends should it include all people who I added
as a friend throughout
47 matches
Mail list logo
