get as
much information to you as we can and listening to your questions and
comments as you create cool applications that integrate with Twitter.
If you want to get ahold of me you can use this Google Group or find
me on Twitter as @themattharris. I'll also be out and about at various
events
://twitter.com/twitterapi and to
this mailing list when we have them.
Thank you to all the developers who have provided us with examples and
datasets of where this has happened to them.
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
Hey everyone,
This week the Twitter Engineering team announced they are running an
annotation Hackfest. The event will be this weekend (29-30 May) at
Twitter HQ (795 Folsom St. San Francisco) and is free to attend.
Places are limited so if you want to attend sign up today!
If you are in the Bay
Great question. We're really excited to see what developers do with
annotations during the hackfest. In some ways the hackfest can be
thought of as an early test of annotations and will let us know what
we have left to do before we release them to the developer community.
The plan, if things go
I've replied on the ticket but for the benefit of everyone here is the
reply:
Thanks. The entities in retweets will function for all retweets from
now on. If you query a timeline which has
retweets in it [1] you should find the entities are included and with
the correct offsets.
1. twurl
Hi Priyanka,
Thanks. We're aware of the problem and it is being tracked as ticket
1650 [1] on the twitter-api issues log.
1. http://code.google.com/p/twitter-api/issues/detail?id=1650
Matt
On May 27, 8:24 pm, newtothisworld priyankalut...@gmail.com wrote:
Hi,
It appears that if you are not
Hey cballou,
What is the actual API call you are making?
I ask because the users/lookup.json method requires you pass it user
ids for it to work. If you don't pass it any user ids or screen names
you will told that no user matches the specified terms.
The data is then returned in an undefined
I'm wondering whether the search is getting popular tweets mixed in
(the default behavior) and that those are what you are seeing.
Can you give an example of one or two of the searches that are doing
this?
Thanks,
Matt
On May 27, 2:19 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
Hi Miles,
Which API method are you using. The preferred method for retrieving
friends and followers is friends/ids [1] and followers/ids [2]. In
both cases it is recommended that you add cursor=-1 to the end.
Matt
1. http://dev.twitter.com/doc/get/friends/ids
2.
Hi cfalar,
This is a known bug and is being tracked as ticket 1404 [1].
Matt
1. http://code.google.com/p/twitter-api/issues/detail?id=1401
On May 27, 12:55 pm, cfalar carolfalard...@hotmail.com wrote:
Hi,
I have a problem with the Search widget.
If i go on this
I just wanted to make everyone aware that this issue is open and being
tracked [1]. Any progress or developments will be posted on that
thread.
If you are experiencing a problem with since_id I encourage you to
read my comment [2].
Thank you,
Matt
1.
Hey Abacadabrados,
You need to give the user lookup request some valid user ids or screen
names. The error you are receiving is because you are sending a
user_id of 0 which is not a valid account. Maybe try with your screen
name first.
You can find more information on how the method works on
Thanks for letting us know about this. You can follow the progress of
this on the issues log [1].
We'll get onto the problem and have it resolved soon.
Matt
1. http://code.google.com/p/twitter-api/issues/detail?id=1668
On May 27, 9:37 am, Steven steven.pul...@gmail.com wrote:
I have noticed a
and improve the documentation.
For those who are interested in knowing about the other projects
please visit the wiki page [1] for a list of them.
Matt
1. http://wiki.github.com/themattharris/annotations-hackfest/
On May 31, 12:56 pm, zbowl...@gmail.com zbowl...@gmail.com wrote:
I was still
Hi Ram,
Thanks for bumping this to our attention. We're aware a number of uses
of source are being missed out and we are tracking this as ticket 1632
on our issues log [1]. You'll be able to track progress on that
thread.
Matt
1. http://code.google.com/p/twitter-api/issues/detail?id=1632
On
Hey everyone,
In March we sent a message to you about upcoming changes to the way
status IDs are sequenced (http://bit.ly/upcoming-status-id-changes).
Today we announced Snowflake - the service we will be using to
generate those new IDs.
It isn't going live yet! We just know a lot of you are
can read more about the supported advanced search operators on the
search site [1].
Hope that helps,
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
1. http://search.twitter.com/operators
On Jun 7, 9:09 am, Jeffrey Greenberg jeffreygreenb...@gmail.com
wrote:
Hello
Hi Andrew,
Thanks for your question. You can file any issues with the docs on
dev.twitter.com on the api-issues list [1]. The list has a component-
docs which you can mark the issue with.
We're working on a number of issues with the docs at the moment and
hope to have them and the rest of the
Hey GHengeveld,
There was a conversation about this back in April which might be help
[1]. In it Taylor explains that OAuth is stateless and that the logged
in state of a user is based on your system rather than ours.
Your application would be interacting with Twitter using the OAuth
tokens for
Hey Craig,
Could you let us see what the authorization header you are sending
looks like (obfuscating your oauth keys and secrets)?
What you're aiming for is a header similar to this:
POST /1/statuses/update.xml HTTP/1.1
Accept: */*
Connection: close
User-Agent: OAuth gem v0.4.0
Content-Type:
Thanks for letting us know about these Andy. As Taylor was saying the
instabilities the other day are likely to have been the cause for
these getting through. It shouldn't happen now but anything that did
get through will still be there.
Matt
On Jun 15, 6:39 pm, Andy Matsubara
Hi Dave,
I seemed to have missed your message originally. Are you still
experiencing problems with this?
In answer to your question there isn't anything special required for
signing requests to send direct messages. If you are still having
problems can you provide us with your signature base
://api.twitter.com/1/direct_messages/new.xml
Extended error response: ?xml version=1.0 encoding=UTF-8?hash
request/1/direct_messages/new.xml/request errorIncorrect
signature/error/hash
On Fri, Jun 18, 2010 at 9:21 AM, themattharris
thematthar...@twitter.comwrote:
Hi Dave,
I seemed to have
Hi Tim,
That error you are getting is often thrown when curl tries to verify
the remote host. You can bypass this check in PHP using:
curl_setopt($link, CURLOPT_SSL_VERIFYPEER, FALSE);
BUT this isn't ideal as it only hides the problem on your server.
Instead, what you need to do is check the
The time format is a little weird and as far as I know, doesn't match
any RFC. Instead it matches the ruby default and is represented in
tokens by:
%a %b %d %H:%M:%S %Z %Y
The format has been like this since the API was first released which
means, for backwards compatibility with other
acmedav...@gmail.com wrote:
I solved the problem.
I did not have an between my two parameters in the POST body.
Adding between the text and user parameter fixed it.
Thanks Matt.
On Jun 21, 1:10 pm, themattharris thematthar...@twitter.com wrote:
Hey Dave,
Looking through your
Hi André,
Looking at your code it looks like you have added the line:
id : 'twitterdiv'
but forgotten to put the comma after it.
If you add the comma the widget will work.
Matt
You don't need the div id = twitterdiv/div as the widget will
automatically create that for you.
On Jun 22, 6:25
, Twitterhttp://twitter.com/themattharris
Due to the high amount of traffic we are seeing at the moment we have
needed to lower the rate limit to 75 to ensure Twitter remains
available to as wide an audience as possible. We are posting updates
as the situation develops on http://status.twitter.com.
Thanks for your patience.
Matt
On Jun
http://twitter.com/themattharris
Hi Nick,
The widgets offer vary basic interaction with Twitter. If they do not
receive results it is likely Twitter is over capacity and results will
become available once service is resumed.
As such, they don't any customizing over the options available on the
widget configuration screen.
If
Hey everyone,
We've been working on the rate limit issue which has been affecting
many of you and believe we now have it fixed. As the issue affected
people in different ways we want to be check your applications are
working again.
If your rate limit is still not resetting please email
* The request you were trying to make
* Any response headers you received
Thanks
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
Hey developers,
Many of you have noticed our SSL certificate for api.twitter.com will
expire on 26th July 2010, with mobile.twitter.com and
search.twitter.com soon after. We wanted to give you a heads up that
tomorrow at 2PM PDT (10PM GMT) we plan to upgrade the SSL certificate
on our servers. As
A quick update on this renewal process..
As the site only fully recovered this morning from the issues of
yesterday we postponed rolling out the new SSL certificates.
We now plan to make the SSL change at 5PM PDT (1AM GMT).
Best,
Matt
On Jul 19, 5:56 pm, themattharris thematthar...@twitter.com
ecosystem.
We'll continue to keep you posted on other developments and changes as
they happen.
Best,
Matt
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
, themattharris wrote:
Hey Developers,
As you might know, this year Twitter launched a suite of Twitter
Promoted Products, including Promoted Tweets (http://blog.twitter.com/
2010/04/hello-world.html) and Promoted Trends, which advertisers can
use to deepen their engagement
/08/pushing-our-tweet-button.html
Best
Matt
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
for
every tweet.
Tom
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via
Hey VC,
Using Twitter for the purpose you describe seems similar to accounts
which provide a notification about a new blog post or a news article.
In those cases some context is provided about the link in the Tweet so
that the timeline is meaningful to somebody who stumbles across it.
You don't
Thanks for the information collected on this. We're investigating this
issue at the moment and updates will be posted to our status blog:
http://status.twitter.com/post/1058895068/investigating-invalid-responses-from-the-api
Matt
On Sep 3, 8:44 am, Marsh Gardiner ma...@apigee.com wrote:
I
/list
Change your membership to this
group:http://groups.google.com/group/twitter-development-talk?hl=en
--
Matt Harris
Developer Advocate, Twitterhttp://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter
Just wanted to let you know we've deployed some changes which should
have fixed this issue.
@themattharris
On Sep 14, 11:38 pm, Remo remo.siegw...@gmail.com wrote:
Hi Matt
Thank you for your response!
The #newtwitter looks great btw!
Cheers
Remo
--
Twitter developer documentation
Just wanted to let you know we've deployed some changes which should
have fixed this issue.
@themattharris
On Sep 8, 8:09 am, Tom van der Woerdt i...@tvdw.eu wrote:
There's currently a bug involving URLs that include an character.
Tom
On 9/8/10 1:02 PM, swati wrote:
script src=http
are
explained on our help site:
http://support.twitter.com/groups/32-something-s-not-working/topics/118-search/articles/66018-my-tweets-or-hashtags-are-missing-from-search-known-issue
Hope that's helpful,
@themattharris
On Sep 21, 8:22 am, Gena01 gen...@gmail.com wrote:
So I've been messing
No new registration is needed, #newtwitter is being rolled out
gradually and at random.
For the API, only the related_results method requires you to have
access to #newtwitter.
Hope that helps,
@themattharris
On Sep 22, 2:22 pm, EastSideDev eastside...@gmail.com wrote:
As app developers, do we
index and how to resolve it.
Best,
@themattharris
On Oct 10, 9:29 pm, Nick nick.fritzkow...@gmail.com wrote:
We are having issues with this as well and it has completely broken
our system.
We have sent many support tickets but have received no response to
them.
It looks to be breaking plain
that one using the Streaming API as well.
Best
@themattharris
On Oct 11, 10:21 am, @IDisposable idisposa...@gmail.com wrote:
The Location search has been VERY unstable, and uses this typical
search:http://search.twitter.com/search.atom?rpp=100geocode=38.627522%2C-90...
It's getting worse
: [
{
name: Matt Harris,
id: 777925,
id_str: 777925,
indices: [
0,
14
],
screen_name: themattharris
}
]
},
text: @themattharris hey how are things?,
annotations: null,
contributors
%3DMy_tokeN
%26oauth_version%3D1.0%26track%3Dtwitter
I hope that helps,
@themattharris
On Oct 25, 3:20 pm, bradley.meck bradley.m...@gmail.com wrote:
Correct, I still had the issue when escaping track= Escaping
params individually did not work either. Still able to tweet though...
Maybe
Hey Chrys,
A couple of things to check first:
1. Have you been granted xAuth access?
2. Double check the timestamp of your request is within 10 or so
minutes of the time returned by Twitter's servers. Our server time is
in UTC.
3. Verify your encoding is correct. For example: a password like ab$
would have expected your URL to look like this:
http://api.twitter.com/1/statuses/home_timeline.json?count=5oauth_co...
page=1
You can read more about signing requests on our developer resources site:
http://dev.twitter.com/pages/auth#signing-requests
Best
@themattharris
Developer
Hi Kevin,
Thanks again for pointing this out. We've updated the gist with a fix
for the issue you identified:
https://gist.github.com/637624
Best,
@themattharris
On Dec 3, 3:23 pm, Matt Harris thematthar...@twitter.com wrote:
Thanks for pointing this out Kevin. I've passed this onto
SSL (https) is supported on some but not all hosts. You can use SSL
on:
* api.twitter.com
* userstream.twitter.com
* betastream.twitter.com
* search.twitter.com
SSL is currently not supported on:
* platform.twitter.com
* widgets.twimg.com
* stream.twitter.com
Best,
@themattharris
Developer
Hi Jenny,
The engineers have said this issue should be fixed but that it may
take some time for the cached data to update. This means things going
forward should be fine but Tweets prior to today may still report the
wrong created_at value.
This only affects REST API queries. The Streaming API
an oauth_token to the request_token endpoint.
Making a request to request_token means you don't have a token already
and want one. So that parameter shouldn't be in that request.
Best,
@themattharris
On Feb 5, 9:10 am, john john.g...@gmail.com wrote:
Matt,
The response is empty, that's what I'm
Just to follow up on this, the correct additional fields are:
profile_image_url_https
profile_background_image_url_https
The original email missed the _url in profile_image_url_https.
Best
@themattharris
On May 16, 3:27 pm, Matt Harris thematthar...@twitter.com wrote:
Hey everyone
the access an
application has requested.
We hope these responses answer your questions. Please continue to send
us your feedback about the permission model and what you would like to
see it offer.
Best,
@themattharris
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API
these questions and answers on the developer
resources site. If your email client doesn't render the responses
above clearly please visit
https://dev.twitter.com/pages/application-permission-model
Best,
@themattharris
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API
Hey everyone,
Thanks for all the information you provided. We were able to reproduce
the problem and the engineers have now released a fix.
You shouldn't receive any garbled API responses anymore, if you do
please let us know.
Best,
@themattharris
On Jun 14, 7:59 pm, michael hazzard miramardes
60 matches
Mail list logo
