Hey Adam,
Thanks for raising this. The website isn't part of the API so we're not in a
position to fix or address the issue. That being said I have checked with
our user support team and know that they are tracking this very issue with
the engineering teams.
From what i've been told the timeline
Hi Steve,
You can use users/lookup to retrieve the details of up to 100
user_ids/screen_names at a time. More information here:
http://dev.twitter.com/doc/get/users/lookup
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Thu, Jan 6, 2011 at 4:28 PM,
Hi Steve,
In answer to your questions.
1. users/lookup returns information about the user_ids or screen_names you
pass to it. You may choose to pay follower ids, friends ids, or both. It's
purpose is to just expand the user_id or screen_name into a hydrated user
object.
2. If you stay within
Hi Yusuke,
Promoted Content is not generally available. Whilst we are testing with a
group of developers there is no timeline for when more developers can apply
for access or if the API will be opened up.
More information can be found in this archived thread:
Hi Joel,
The API will only return mentions for the authenticating user. To retrieve
mentions for other users you would need to use the Search API or 'follow'
the user_id through the Streaming API.
Hope that helps,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On
ticket submission. Please try again later.
Tried more than once and got nothing.
I'm really blind here, have no idea what's happening... Anyone can
help?
Thanks,
Alexandre Cisneiros.
On Jan 4, 4:27 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Alexandre,
You should be able to access
23043372398673920 is shown in new twitter,
but not in the website view.
Thanks for the info though,
Adam
On Jan 6, 2:48 pm, Matt Harris thematthar...@twitter.com wrote:
Hey Adam,
Thanks for raising this. The website isn't part of the API so we're not in a
position to fix or address the issue
:
test**test
On Tue, Jan 4, 2011 at 8:57 PM, Matt Harris thematthar...@twitter.com
wrote:
Hi Adam,
That's correct, a tweet cannot be just a * or a * word. Something
like
** or * html { would be fine though.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com
Hi Rocky,
Your callback domain looks to be missing the slash separating the domain
from the querystring. Try instead the format (notice the slash before the
?):
http://MyDomain.com/?ReturnUrl=/test.aspx
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On
Hi Adam,
The following policy documents explain a little bit more about how we
approach this and what steps are available for you to take:
Trademark: http://support.twitter.com/entries/18367-trademark-policy
Impersonation: http://support.twitter.com/entries/18366-impersonation-policy
Inactive
Hi,
The Tweet Button doesn't provide any action hooks or callbacks. It is
intended that the button initiate the Tweet flow. What different action did
you have in mind?
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Jan 7, 2011 at 3:48 AM, nebur
Hi,
Thanks for letting us know about this. Could you file a ticket on our issues
tracker so we can track any progress. The issues lists can be found at this
URL:
http://code.google.com/p/twitter-api/issues/list
Thanks,
@themattharris
Developer Advocate, Twitter
Hey Andy,
Glad to hear that worked out for you. Thanks for letting us know!
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Jan 7, 2011 at 11:13 AM, Andy abowl...@gmail.com wrote:
And that fixed it - the encoding that was happening when I built the
Hey Brian,
When you use the Streaming API filter method we will stream to you all the
Tweets which match your track terms - up to your allowed sample size.
What this means is over the course of a sampling window we apply your track
terms to the full firehose, and then return as many results as
Hi Gabe,
We have a page about OAuth Echo on our Developer Resources site:
http://dev.twitter.com/pages/oauth_echo
Let us know if you have any questions which arise from it,
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Jan 8, 2011 at 4:04 PM,
When validating for XHTML you need to ensure the in URLs is encoded as
amp;
In your case that would mean using:
http://platform.twitter.com/anywhere.js?id=4MefUUvPXcQdIm30HhQamp;v=1
and
http://www.twitter.com/share?url=minha_urlamp;text=meu_textoamp;count=horizontalamp;via=fabriciorgomes
Hey everyone,
Starting today we will be streaming unfollow events through Site Streams.
These events are being streamed to allow you to keep the social graph of
your users current without the need to query the REST API.
We require that you only surface actions that are organically displayed on
Hi Murray,
This was discussed not so long ago in another thread which you can find
here:
http://groups.google.com/group/twitter-development-talk/msg/3422529031509f31
Hope that answers your question,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Jan 15,
Hi Ran,
The users email address is not made available through the Twitter APIs.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Jan 15, 2011 at 1:44 AM, Ran Margaliot ran5...@gmail.com wrote:
Hello, is it possible, using the twitter api, to get a
Hi,
Basic Authentication is not supported on the REST API and instead you must
authenticate using OAuth. You can find more information about migrating from
Basic to OAuth on our developer resources site:
http://dev.twitter.com/pages/basic_to_oauth
Best,
@themattharris
Developer Advocate,
Hi Toddy,
The users/lookup method, which lookupUsers calls, will only return that
error if none of the user_ids/screen_names you provide are recognised. The
behavior of the API method is such that only the recognised
user_ids/screen_names are returned and any which are not found are left out
of
Hi Thomas,
The timestamp must be the current time in epoch seconds. By design the epoch
time is in GMT, which is the same as Twitter's servers so you shouldn't need
to adjust it. If you do it implies your server clock isn't set correctly.
Looking at your code you have a lot going on which
Hey Jordan,
When I run your request in my code I get the details of all 5 users. To help
us track down the problem can you share the raw HTTP request and response?
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Jan 17, 2011 at 7:32 AM, Jordan Glasner
:
Hi Matt,
Thanks for the explanation. I will file the bug report. I'd like to
hear more about the sample size. I've read through the Streaming API
docs a lot, and I haven't come across anything specific about the rate
limits. Where can I read more?
Brian Maso
On Jan 10, 5:24 pm, Matt
Hi Kevin,
This is a feature on the teams roadmap. We don't have a timeline for when or
if this will be implemented but we know it's something developers would like
to see. If anything does happen it will be communicated either through
@twitterapi or this mailing list.
Best,
@themattharris
Hi jarón,
Each Tweet contains a retweet_count which tells you the number of times a
Tweet has been retweeted (up to 100). Then, to find out the person who last
retweeted a Tweet you can call /1/statuses/retweets/:id .
You can learn more about the API request on our developer resources site:
Hi,
We do not allow developers or applications to login using OAuth access
tokens.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Jan 10, 2011 at 3:26 PM, ano0810 luv@gmail.com wrote:
is there a possibility to get to the user's home page on
Hi Mesut,
The Javascript API is considered part of the @anywhere internals and is not
supported by us. You are free to experiment with the API but be aware
functions may stop working or change without notice.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On
/themattharris
On Thu, Jan 20, 2011 at 11:57 AM, FPN fpnew...@gmail.com wrote:
I'm having the same problem. Did this bug get resolved?
Thanks in advance ... Frank
On Jan 3, 6:50 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Aaron,
The engineers are aware of this error and are looking
1 2010, 3:36 am, Matt Harris thematthar...@twitter.com wrote:
This is unexpected. Can you provide us with some sample Tweet IDs where
those fields are different so we can investigate further.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
)?
By the way I have question - what is the retry policy for the APIs? Is
the retry counted as a new call? Also, is there any chance that my
application gets throttled even more because it makes frequent calls
to lookup?
Thanks!
Toddy
On Jan 18, 5:13 pm, Matt Harris thematthar
Hey,
SSL is supported by Search. You can find the other API URLs and whether they
support SSL or not in this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/46ca6fcb9ea7eb49/f0f818daee475666
Best,
@themattharris
Developer Advocate, Twitter
Hey to you all,
Feedback about the Details Pane has been great but we are focusing on other
projects right now. This means we aren't starting any new partner
integrations at this time.
We are excited to get more publishers into the program though, so when we
start accepting new integrations we'll
Hi,
Are you still seeing this issue?
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Jan 24, 2011 at 1:34 PM, dt dtip...@gmail.com wrote:
I pull json results from a url like this:
Hi Zhe,
The information is provided by the application making the status/update API
call. How that information is gathered is application and device specific.
It could be manually chosen by the user of the application, or identified
using the GPS in the device. Some devices may choose to use the
We don't support the X-Accept-Encoding header and there are no plans for it
to be added to the API. I'm not familiar with the roadmap for
Silverlight/Windows Phone development but suggest they are the best place to
ask about unlocking the ability to set those headers.
Best
@themattharris
Hey Ed,
Is this still happening. I know the team made some changes recently which
may have caused this but I thought it was resolved.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Jan 24, 2011 at 4:49 PM, M. Edward (Ed) Borasky
If the rate limit has been reached for your connection the widget is unable
to display Tweets. This is something the team is aware of but doesn't have a
timeline for solving yet.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Tue, Jan 25, 2011 at 6:56 AM,
Hi Zhe,
The Search API can only return approx 1800 per query. Creating a radius that
covers the whole earth would be counter productive.
Instead you may wish to use the Streaming API. Using this API you can say
that you want all Geocoded Tweets from around the world. If you do that any
Tweet
Hi Maanik,
In addition to the 401 header, the body of the response the API returns to
you contains a reason for the access being rejected. The reason will be
something like invalid timestamp or incorrect signature and knowing what
it is will tell you which part of your API request needs
Hi Srikanth,
You can find out more about the Business Services Twitter offers on our
dedicated Business website:
http://business.twitter.com/
Hope that helps,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Jan 29, 2011 at 11:18 PM, Srikanth
You can forward to me and I can route it to the right place.
Thanks!
Matt
On Jan 31, 2011, at 15:53, M. Edward (Ed) Borasky
zn...@borasky-research.net wrote:
On Mon, 31 Jan 2011 15:47:48 -0800, Matt Harris thematthar...@twitter.com
wrote:
Hey Ed,
Is this still happening. I know the team
nonspace
characters?
On Jan 31, 5:01 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Zhe,
At present the Streaming API is unable to match filter keywords for
languages who do not separate words or phrases with spaces.
This is because we currently tokenize (split) Tweets around spaces
Hi Kyle,
The Trends endpoints only support the JSON format. The details for the API
method can be found on our developer resources site:
http://dev.twitter.com/doc/get/trends
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Tue, Feb 1, 2011 at 9:20 AM,
Hi Leon,
Have you considered using the users/lookup method instead of users/show?
users/lookup allows you to retrieve the details of up to 100 user_ids or
screen_names in a single request.
There is more information about this method on our developer resources site:
Hey Adam,
Do you include the parameter include_rts=1 ? Be default
statuses/user_timeline doesn't include retweets so you have to add this
parameter to retrieve a full timeline.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Feb 2, 2011 at 2:28 PM, Adam
Hi John,
What is the does the body of the error response say? The message will tell you
which part of the oauth request failed.
Also be aware that oauth timestamps are in UTC seconds.
Best,
@themattharris
On Feb 4, 2011, at 12:45, john john.g...@gmail.com wrote:
I have an application that
found the
section of the library I'm using that creates the UTC timestamp, by
calling time.time(). I would think that Django's timezone property
would set the runtime timezone, however I have not checked that
specifically. Any ideas?
Thanks,
John
On Feb 4, 4:58 pm, Matt Harris mhar
Hi Choock,
Twitpic is a 3rd party service so they would no more about their API. That
being said the OAuth Echo parameter is X-Auth-Service-Provider so it sounds
like, by changing the header, you're not using OAuth Echo now.
In addition, TwitPics documentation states the parameter the same as
:
Thank you Matt, please see below
On 8 фев, 02:00, Matt Harris thematthar...@twitter.com wrote:
Hi Choock,
Twitpic is a 3rd party service so they would no more about their API.
That
being said the OAuth Echo parameter is X-Auth-Service-Provider so it
sounds
like, by changing the header
HI Peter,
I'm glad you have this working. Just to explain the @anywhere JS-API isn't
documented because it's not supported by Twitter. This is because the JS-API
is considered part of the internals of @anywhere, which means it could
change without notice at anytime.
Best,
@themattharris
Hi Dale,
There are a number of things that can cause OAuth to fail. We've clarified
our error messages to try and make it easier to know which bit is the cause
of the problem.
For timestamps we return the error message Timestamp out of bounds.
In your case the error message is saying your
Hi Craig,
Can you you share the actual requests you are making, including the OAuth
parameters you are sending. I can then take a look at what might be
happening. Also, if you can let me know your screen_name I can see if I get
the same response querying your user_timeline.
Best,
@themattharris
Hi David,
We use the lat/lon sent to us when the Tweet is created. How that lat/lon is
retrieved depends on the device being used to send the Tweet. The content of
the Tweet is not used to populate the lat/lon coordinates.
A couple of reasons for why it could be reported like this:
* The user is
If you include the parameter include_entities=1 in your request we will
return an extra object in the response telling you where the hashtags,
mentions and URLs are in the Tweet.
You can learn more about Tweet Entities on our developer resources site:
Latitude, also erratic (mostly incorrect) but in a completely different way
to Twitter's result.
Thanks again,
David
David Terranova
*davidterranova.com | rebelrave.tv*
On Feb 9, 2011, at 2:01 PM, Matt Harris wrote:
Hi David,
We use the lat/lon sent to us when the Tweet is created. How
with my personal
account and always got back 20 results.
Maybe this *is* an issue on Twitter's side, with accounts that have a
small number of tweets?
On Feb 8, 10:01 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Craig,
Can you you share the actual requests you are making
Hi Ian,
For trends you might like to try our trends.api.twitter.com server which
hosts a cached copy of the trends information and is updated whenever the
trends change. It should support your use case and we would be interested in
any feedback you may have about it's performance.
To use it just
Driven Web
http://www.ConnectedThinking.com
Twendr : Your Global Twitter Dashboard : What's happening Now!
http://www.Twendr.com
On Feb 10, 8:40 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Ian,
For trends you might like to try our trends.api.twitter.com server which
hosts a cached
me at : http://samuraism.jp/
On Feb 11, 2011, at 10:40 , Matt Harris wrote:
Hi Ian,
For trends you might like to try our trends.api.twitter.com server which
hosts a cached copy of the trends information and is updated whenever the
trends change. It should support your use case and we
Hi Nashi,
This is a known issue our engineers have been made aware of. We'll post
updates to the ticket as they become available:
http://code.google.com/p/twitter-api/issues/detail?id=2045
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Feb 14,
Hi Pamela,
I'm not able to reproduce this problem when I try and share you're URL. Can
you share the HTML you are using to implement the Tweet Button so we can
test ourselves as well.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Tue, Feb 15, 2011 at 8:18
Hi Leon,
We don't expose that information through the API or on twitter.com so
keeping a record yourself is the best approach.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Feb 16, 2011 at 3:06 AM, Leon Meijer l...@lmeijer.nl wrote:
Hello all,
The Twitter App for Facebook isn't something the platform team maintains so
we're not able to help diagnose the problem. Instead you should contact our
user support team so they can help you out. You can reach them through this
URL:
http://bit.ly/gottaproblem
Best,
@themattharris
Developer
Hi Zhe Chen,
It is possible for the streaming connection to restart or disconnect you.
There are a few reasons why this can happen and all are explained in our
Streaming API concepts document. Approaches on how to deal with disconnects
are also explained in the document.
You can find the
Hi,
Maybe Twitter Lists could help you achieve this:
http://support.twitter.com/entries/76460-how-to-use-twitter-lists
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Feb 16, 2011 at 5:52 AM, EazySPR98 chall...@gmail.com wrote:
It would be a good
This information is returned in the users profile information and can be
access from the API something like:
/1/users/show -- http://dev.twitter.com/doc/get/users/show
/1/users/lookup -- http://dev.twitter.com/doc/get/users/lookup
You could also request a users friends IDs using
/1/friends/ids
Hi Eric and Aci,
Do you have some example tweets showing what you mean?
Thanks,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Feb 16, 2011 at 11:22 PM, Eric Charles
eric.umg.char...@gmail.comwrote:
Same question here.
Eric
On Feb 17, 12:59 am, aci
Hey Del, David,
The API request for doing this is /1/statuses/home_timeline but this is for
your viewing only. You must not use that timeline to render Tweets on a
public website. The reason for this is your home_timeline could contain
Tweets from protected users that you follow, and displaying
if needed.
On Thu, Feb 17, 2011 at 3:31 PM, Matt Harris thematthar...@twitter.comwrote:
Hi Eric and Aci,
Do you have some example tweets showing what you mean?
Thanks,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Feb 16, 2011 at 11:22 PM, Eric Charles
Cross posting this reply as it is relevant.
Our support team confirms that Tweeting with locations is disabled at the
moment.
http://twitter.com/Support/status/37747170618785793
When the service is restored @support will post an update.
Best,
@themattharris
Developer Advocate, Twitter
Hi Josiah,
OAuth is working fine in my tests of the Streaming API. If you are getting
errors double check you are encoding the commas correctly in your
basestring.
For example, if your track terms were:
track=twitter,twitter api,twitterapi
The basestring should include:
Hi Zaver,
A 420 response from the Search API means you have been rate limited. What
you should do is stop making requests and then try again 30 seconds later.
If you still get 420, wait 1 minute. Continue doubling the time you wait
until the 420 stops and you get results. Then gradually increase
Hey Josiah,
Glad you got it working.
I have an OAuth library I put together which you might want to look at. It's
in PHP and shows the OAuth signing process. It also supports multipart
uploads and the Streaming API. You can find it on github:
https://github.com/themattharris/tmhOAuth
Best,
Hi Seth,
Twaud.io isn't part of the Twitter API but i'll try and help you anyway.
The first thing to note is the Headers should be of the
format X-Verify-Credentials-Authorization. The
x_verify_credentials_authorization is mentioned because Twaud.io supports
the OAuth Echo parameters in the
/themattharris
On Tue, Feb 22, 2011 at 11:19 PM, Umashankar Das umashankar...@gmail.comwrote:
Hi Matt,
Do the failed requests count [one's with 420 response] into the tally
for the next hour?
Regards
Umashankar Das
On Wed, Feb 23, 2011 at 12:41 PM, Matt Harris
thematthar
Hi J,
The authoritative information for the Streaming API is under the /pages/
path and you should use that for guidance.
The number of connections you are allowed to the Streaming API is described
in the Streaming API Concepts document:
http://dev.twitter.com/pages/streaming_api_concepts
Hey Zaver,
Repeating the query should work. If the error is persistent let us know what
the term is so we can take a look.
Best,
@themattharris
On Feb 25, 2011, at 10:09, zaver zave...@hotmail.com wrote:
Hello,
I ve been getting a 500 response code lately on searching some
keywords.
Hey there,
You should have an email from our support team about this. If not I recommend
contacting the team with the information about your application. They handle
things like this and will be able to tell you more.
You can reach them through:
a...@twitter.com
Best
@themattharris
On
Hi Harry,
Which library are you using and how is it passing the parameters to the
streaming API? Also, are you using any other filter parameters when
connecting to the Streaming API?
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Feb 25, 2011 at 9:59
Hi Paresh,
The Streaming API supports any latitude and longitude bounding boxes but
relies on Tweets being geocoded. If the quantity of Tweets being returned is
low it could that Twitter users in India do not geocode their Tweets, or the
devices they use do not support geocoding
Hope that
Hi Dheeraj,
Twitter does not share email addresses through the API. If you wish to know
a users email address you would need to ask them for it through your own
application.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Feb 26, 2011 at 5:28 AM,
Hi J,
Glad you worked it out. The Streaming API (stream.twitter.com) does not
support multiple streams - only one connection is permitted. This is
explained in more detail on our developer resources site:
http://dev.twitter.com/pages/streaming_api_concepts#access-rate-limiting
Best,
wrote:
Hi Matt,
I am using *phirehose* and *not* passing anything else beside the
$streamsetLocations
Thanks
Harry
On Mon, Feb 28, 2011 at 2:07 PM, Matt Harris thematthar...@twitter.comwrote:
Hi Harry,
Which library are you using and how is it passing the parameters to the
streaming
Hi Mohorad,
Most of the Twitter APIs support multiple response formats. The most common
formats are XML and JSON but some methods also support RSS and ATOM.
The response format is controlled by changing the extension of the method.
For example:
http://search.twitter.com/search.json will
Hi to you both:
Ken: The API should be rejecting the duplicates. Do you have an example
where the duplicate is being allowed through?
Tammy: The guidelines for automated Tweets can be found on our support site.
Some helpful resources are:
Hey Rob,
Can you share the exact URL you are requesting. When I use the count
parameter with a value of 1 I only get 1 tweet back. The URL I am requesting
looks like this:
https://api.twitter.com/1/statuses/home_timeline.json?count=1
Best,
@themattharris
Developer Advocate, Twitter
Hey Hugo,
The rate limit you refer to is for the REST API only.
The Search API, which it looks like your using, has it's own rate limiting
system external to the REST API.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Mar 9, 2011 at 2:38 PM, Hugo W
Hi Jerry,
Can you tell me a little bit more about where you are making this request
from. Is it user facing code or server side?
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Mar 11, 2011 at 7:06 AM, Jerry Thompson jerrycando...@gmail.comwrote:
Hi,
Hi Jeong, Kyeonghun.,
So we can help you out could you share the code you use and the error you
are getting when you try and Tweet.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Thu, Mar 10, 2011 at 11:04 PM, Kyung Hun Jeong deux...@gmail.com wrote:
Hey,
Can you tell me which button is causing this popup error so we can take a
look.
Thanks,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Mar 11, 2011 at 11:36 AM, BFritchie brfritc...@gmail.com wrote:
I am using a Profile Widget
Hi there,
Could you give a few examples and maybe a screenshot showing this so we can
investigate.
Thanks
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Mar 11, 2011 at 2:39 PM, CSobolewski wiglyw...@gmail.com wrote:
I have a script which is using the
Innovation and development with the APIs are not being prevented. There have
always been guidelines, and rules of the road so we all know what is and isn't
allowed.
If you build a client you are touching the majority of Twitter features. The
APIs allow you to do this, and Twitter and your
Hi Trevor,
Could you share the request and response you are sending so we can
investigate. Remember to obscure user and consumer secrets.
Thanks,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Sat, Mar 19, 2011 at 5:47 AM, Trevor Dean trevord...@gmail.com wrote:
Hi,
The error message Failed to validate oauth signature and token does mean
either the signature you are sending, or the consumer token is invalid.
Could you share the request you are making, and response you are getting.
Remember to obscure any user or consumer secrets.
Best,
@themattharris
Hi Arnaud,
Did you authenticate your request with OAuth?
The API method users/search requires authentication to work. users/show
doesn't which is why you may find one worked while the other one didn't.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon,
Hey Jimmy,
You can find a list of the available trends locations by calling the API
method trends/available. More information on this method can be found on our
developer resources site:
http://dev.twitter.com/doc/get/trends/available
Best,
@themattharris
Developer Advocate, Twitter
Hi Suresh,
The text that appears after the 'via' in a Tweet is read from your
application details. The name of the application and it's URL are specified
when you create an application on:
http://dev.twitter.com/apps/new
The application source does not support images, only text can be used.
In many cases we are forced to change the rate limits in response to
a significant increase in requests, which means it isn't always possible to
give advanced notice of rate limit changes.
For some of you it sounds like your code that handles rate limiting didn't
react appropriately. When
Remember Search only indexes Tweets for approximately the last 6-7 days. The
help article Taylor linked to explains this and some of the other reasons
why accounts may not show in Twitter Search:
401 - 500 of 605 matches
Mail list logo
