Anybody experiencing the same problem?
On Jul 6, 2:32 pm, Arnaud arnaud.meun...@twitoaster.com wrote:
Hello,
I am experiencing a strange problem (bug?) with the /statuses/show
method on a specific status ID: n° 2490912395. The problem is
occurring since 2009-07-06 03:16:11 UTC.
Could you
pulled it unauthenticated and it worked fine. It was probably just a
temporary Twitter bug.
https://twitter.com/statuses/show/2490912395.xml
Abraham
On Tue, Jul 7, 2009 at 07:59, Arnaud Meunier
arnaud.meun...@twitoaster.comwrote:
Anybody experiencing the same problem?
On Jul 6, 2:32 pm
Another example of a status affected by this bug:
https://twitter.com/statuses/show/2514621302.json
Once more, only JSON format seems to be failing.
Arnaud.
On Jul 7, 4:21 pm, Arnaud Meunier arnaud.meun...@twitoaster.com
wrote:
The bug is only occuring in JSON format. Try this :
https
Just did it:
http://code.google.com/p/twitter-api/issues/detail?id=797
On Jul 7, 6:38 pm, JDG ghil...@gmail.com wrote:
Seems like you should be opening a bug.
On Tue, Jul 7, 2009 at 10:31, Arnaud Meunier
arnaud.meun...@twitoaster.comwrote:
Another example of a status affected
Same problem here, all my Oauth requests are receiving a Could not
authenticate you. answer with a 401. Don't understand why, I didn't
change anything, and this just started to happen a few minutes ago.
The application type is Browser, with the Twitter for login option.
Quite a big problem on my
The problem is known, cf this thread, for example:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/39306c36ecc9cdb8
Matt has also updated the twitterapi account to let us know he was
working on it.
Arnaud.
On Jul 10, 1:56 am, goodtest goodtest...@gmail.com wrote:
On my side, things are back to normal since Matt announcement.
On the previous bug, the error message attached in the body was Could
not authenticate you. Are you receiving the same error message?
Arnaud.
On Jul 10, 1:34 am, johann romef...@gmail.com wrote:
Hi,
Same here, we re getting 401
Roelands duane.roela...@gmail.com wrote:
I'm getting the same thing I was getting earlier: 401 Unauthorized
On Jul 9, 10:16 pm, Arnaud Meunier arnaud.meun...@twitoaster.com
wrote:
On my side, things are back to normal since Matt announcement.
On the previous bug, the error message attached
I always heard IP whitelisting was taking precedence to account rate
limits.
What you're describing sounds like the normal behaviour to me.
Arnaud.
On Jul 10, 6:06 am, alan_b ala...@gmail.com wrote:
I'm making a account/rate_limit_status call using OAuth authenticated
with a non-whitelisted
--
Arnaud Meunier
Twitoaster | http://twitoaster.com
, not just weeks or
just recently...
On Jul 10, 1:17 pm, Dossy Shiobara do...@panoptic.com wrote:
On 7/10/09 3:38 PM, Jeffrey Greenberg wrote:
Just to say it, this has been going on for weeks
Actually, months ... at least as far as I've noticed it.
--
Arnaud Meunier
Twitoaster
Twitter Dev
* = Who just said Hi, Dr. Nick. out loud? Your cube neighbor thinks
you're crazy.
--
Arnaud Meunier
Twitoaster | http://twitoaster.com
Since yesterday, my application’s main account (@twitoaster) received
two abnormal 401 errors (both during a POST Request). There are
strictly no reasons for such errors to be received (the same requests
succeeded a few minutes later) and I was wondering if someone else had
recently experienced
Guess it might interest some of you; I just made public the Twitoaster
API ( http://twitoaster.com/api/ ).
Using the same model as the Twitter one, it brings the following
methods:
- conversation/show: Returns the whole conversation (max 200 tweets)
containing the requested tweet.
-
This has already been told, but a better support for mobiles and poor/
old rendering browsers is a must. Something as simple as using the
useragent to display a nice, working and adapted login page would be a
great start.
Another point would be reliability. Is there a way that you priorize
oAuth
Hi,
One of my members cannot connect with a specific account, where other
accounts work. The account is not suspended. Every login try ends with
a OK, you've denied *Twitoaster* access to interact with your
account!.
Account name is @msbookish. Anyone would have experienced that kind
of
The user was authenticating with firefox and this plugin:
https://addons.mozilla.org/en-US/firefox/addon/750
Desactivating the plugin solved the problem.
Hoping that will be useful, if someone already experienced a similar
case,
Arnaud.
On Oct 22, 10:58 pm, Arnaud Meunier arnaud.meun
On my side, I heard it was based on the top trending applications from
the week. In any case, developers are not able to request or submit
their application for placement. Probably because everybody would love
to see his app featured there :)
Arnaud.
Twitoaster | http://twitoaster.com
On Feb
Hello folks,
My name is Arnaud Meunier and I'm a Paris-based Twitter Developer
Web Entrepreneur. I built http://twitoaster.com a real-time (thanks to
the streaming API) conversation threading service / client helping
people and businesses to improve and optimize the way they communicate
Really excited to be in San Francisco (first time for me there) next
week! Quite a long trip from Paris, but I just couldn't miss such an
occasion to meet you all :)
For those who would be interested, I made a little Chirp page on
Twitoaster, threading Attendees' conversations in real time:
(but this part
recently disappeared from the schedule). I’m also wondering how I’ll
manage to stay awake for 48h+ :)
Arnaud Meunier - http://twitter.com/twitoaster
Twitoaster - http://twitoaster.com
PS: For those who would have missed them, here are a couple of links
about the conference:
- Pre
developer ecosystem from this Google Group, to GitHub, StackOverflow
and Twitter. If I get the chance I'll also be adding some refinements
to a soon to be launched app I'm woking on -http://smidgn.com
See you next week!
Jonhttp://twitter.com/jot
On Thu, Apr 8, 2010 at 7:13 PM, Arnaud Meunier
We shouldn’t “fill holes” anymore, Wilson said. The thing is Twitter
has deliberately kept a lot of holes opened, encouraging us to fill
them (and lots of applications have been doing it with innovation, by
the way).
Now we’re supposed to dig, create new holes, and fill them. Okay!
There are a
+1 for the metaphors :)
We all know what Twitter would like to see. No surprise here, nothing
extraordinary, just advices we already were aware of. I mean... Who
intended to code another photo sharing service or another desktop
client before these annoucements? I guess nobody.
Anybody who has
Thanks for this clarification, Ryan.
I think an important part of the tension is coming from the fact you really
took your time to (as you say) dig a little bit, and realize the right
move was to buy Tweetie. I mean, it’s almost like if it was in Twitter core
to... have multiple holes, and
Nice! But... I couldn't miss this opportunity to share my own version
of Chirp tweet tracking page, focused on conversations! :p
http://twitoaster.com/twitter-chirp-conference/
It threads in real time all attendees' conversations, displaying their
discussions rather than disjointed tweets.
Enjoying a free Saturday afternoon, I was playing with @Anywhere and I
noticed something quite strange related to Twitter Usernames. The
@Anywhere documentation says A Twitter screen name is an '@' symbol
followed by 1 to 20 alphanumeric characters, including underscores
The problem is… I thought
Which features are you actually thinking about? Except the « Signup »
feature, I didn’t see anyhing that couldn’t be reproduced on another
third party client using the Twitter API…
Arnaud Meunier | @twitoaster
http://twitoaster.com
On 19 mai, 13:17, Rich rhyl...@gmail.com wrote:
So Tweetie
Hey Felipe,
If you checked the Always use HTTPS box in your Account settings, the
Share this on Twitter popup (that appears when you actually click the
button) will be served over SSL.
However, the button itself doesn't work over SSL yet (cf:
http://dev.twitter.com/pages/tweet_button_faq#https).
Hey Jacob,
Valid SSL certificates are installed on si[0-5].twimg.com subdomains. On
your SSL served pages, you could simply replace http://a; with
https://si;. Example
for the @twitter account:
- HTTP: http://a3.twimg.com/profile_images/1124040897/at-twitter_normal.png
- HTTPS:
Hey Alex,
I don't know in which context you plan to use this search widget, but trying
to make your search results kid-friendly with simple bad-words filtering
doesn't look very realistic. What about a manually curated list of tweets?
Did you have a chance to take a look on the Faves widget, for
Hey Abby,
You won't be able to find the t logo because we replaced it with the
bird logo. As stated in the page you linked to (Guidelines for use of the
Twitter trademark - http://support.twitter.com/entries/77641) you
should use the most recent version of our logos (which is a bird if you're
Hey,
Simply set the data-count property to none. For more information, read the
doc: http://dev.twitter.com/pages/tweet_button#position-count
Arnaud / @rno http://twitter.com/rno
On Fri, Mar 25, 2011 at 9:03 AM, twitter dev dev.at.twit...@gmail.comwrote:
HI Guys,
I'm using the following
Hey Chris,
1) Is the IP you're using shared? For example, what was the value of
X-RateLimit-Remaining _before_ starting the test? If you're concerned with
Rate Limiting, you should really consider authenticating your calls.
2) Looks like you're not using your library correctly for search. Try:
As Tatham said, each access token gives you up to 350 GET Request per hours.
Make some requests (signing them with different access tokens) and look at
the X-RateLimit-Remaining header.
Arnaud / @rno
On Mon, Mar 28, 2011 at 6:29 PM, Tatham Oddie tat...@oddie.com.au wrote:
If you use their
Hey Riley,
You should use users/lookup, with the screen_name parameter (up to 100
are allowed in a single request). Not sure to get what you mean by the
OAuth of the users I am looking up? The only thing you need is to sign your
request.
Arnaud / @rno
On Mon, Mar 28, 2011 at 1:14 PM, Riley
Hey,
The easiest way would be be to use the iframe version of the Tweet Button:
http://dev.twitter.com/pages/tweet_button#using-an-iframe
Arnaud / @rno
On Mon, Mar 28, 2011 at 5:46 AM, powtac pow...@gmx.de wrote:
I have a asynchronous page where I want to place a Twitter Tweet
Button. But
This particular problem only concerns a couple of users who didn't re-upload
their profile image since we had this bug in 2009. Unfortunately, a fix is
unlikely to come.
In most of the cases, image size is correct. If it's just about displaying
these images in a browser, you can set the image
Hey Tom,
You probably want to pay the most attention to the X-RateLimit-Remaining
header, which is the number of requests you can make before being
rate-limited. It's a good practice to monitor this value and throttle your
requests if necessary.
The X-RateLimit-Reset timestamp indicates when
Hey Steve,
No suggestion will be made if the user tweeting is already following you.
Cf http://dev.twitter.com/pages/tweet_button#related
By the way, your account is already going to be shown, thanks to the
data-via parmeter. There's no need to use data-related in your case.
Arnaud / @rno
Search API rate limiting is not handled like other endpoints of the REST
API. As explained on http://dev.twitter.com/pages/rate-limiting#search, the
Search Rate Limit isn't made public to discourage unnecessary search usage.
Concerning the User-Agent, use something like Your App Name - Version
Hey Chris,
The endpoint is working fine with both parameters (just tested it).
If you're still having this issue, think to provide more details (i.e.
request sent with auth headers + Full HTTP response). Otherwise, people of
this Mailing List won't be able to help you that much!
Arnaud / @rno
Hey Rami,
The tweet button doesn't support Arabic language (cf.
http://dev.twitter.com/pages/tweet_button_faq#languages). Now you can still
build your own tweet button in order to replace Tweet by its translation
in Arabic (cf. http://dev.twitter.com/pages/tweet_button#build-your-own),
but the
( 'user' =
19081905, 'text' = $text ) );
Using screen_name has been working for 4 months in our app, and
stopped working 2 days ago.
Thanks
On Apr 5, 10:02 pm, Arnaud Meunier arn...@twitter.com wrote:
Hey Chris,
The endpoint is working fine with both parameters (just tested
Hey Idan,
The doc is indeed outdated, thanks for reporting it. The following lists
endpoints do not require authentication:
- /1/:user/lists/:id
- /1/:user/lists/memberships
- /1/:user/lists/subscriptions
Arnaud / @rno http://twitter.com/rno
On Sun, Apr 10, 2011 at 3:31 AM, Idan Gazit
As Tom said, you should use web intents if you're looking for a simple
tweet link. It's really easy to implement, it doesn't require javascript,
and it's mobile friendly. Oh, and you can also use the related and via
parameters (if you like Tweet Button's suggested account system).
More info on
My guess is you probably just received an HTTP 502 (FailWhale) at some
point, this breaking your loop. What was the last HTTP response you received
(including headers)? If it's a 502 error, just handle it in your loop (i.e.
retrying after 10 seconds), and eventually reduce the count if that
Hey Alin,
What do you mean by *I authenticated, verified the credentials and **
queried*? In this context (API call) authenticating means signing your
request using OAuth. Signing-in with your account on twitter.com is a
completely different thing and has no effect on your API requests.
Arnaud /
Why would you think I was talking about signing in on twitter.com
when I was talking about verifying credential?
On Apr 11, 10:11 pm, Arnaud Meunier arn...@twitter.com wrote:
Hey Alin,
What do you mean by *I authenticated, verified the credentials and **
queried*? In this context (API call
Hey Anu,
The tweet button currently doesn't support callbacks. However, there's this
Enhancement ticket you can vote for:
http://code.google.com/p/twitter-api/issues/detail?id=1835
Arnaud / @rno http://twitter.com/rno
On Mon, Apr 11, 2011 at 10:39 PM, anu anu...@gmail.com wrote:
Hi all,
I
Hey Daniel,
You can make up to 350 authenticated GET requests, per token (user), per
hour.
So yes, the example you describe is supported :)
Arnaud / @rno http://twitter.com/rno
On Sat, Apr 16, 2011 at 6:08 AM, pan daniel danielpa...@gmail.com wrote:
Hi,
I have read the api document and
That's the problem with shared hosting IP addresses. I encourage you to sign
all your requests using Oauth (http://dev.twitter.com/pages/auth) even if
they don't require authentication. If you're not familiar with OAuth, take a
look on these .NET Twitter libraries:
Hey Konstantin,
OAuth is just an authorization/authentication mechanism. It's not handling
user sessions. You'll have to implement it on your side.
Now depending on what you want to do, you might be interested by web intents
as they'll handle sessions mechanism for you (automatically detecting
Hey Vijay,
If you retrieve your account's tweets through the API, you'll see each
status object has a source attribute. If you already coded something to
fetch / display your tweets through the /1/statuses/user_timeline endpoint,
you'll just have to filter the tweets by checking this source
Hey Ton,
There was a similar discussion on this ML a few days ago:
http://bit.ly/icFfcC
We do not expire access_token (unless a user explicitly rejects you app) so
you don't have to go through the whole OAuth dance once someone approved
your app. Store your user's access_token and implement a
: if the timerbased limit-reset takes place do you
need a to login again or can you just start posting again.
On Apr 18, 6:29 pm, Arnaud Meunier arn...@twitter.com wrote:
Hey Ton,
There was a similar discussion on this ML a few days ago:
http://bit.ly/icFfcC
We do not expire access_token (unless
Hey Ozgur,
This is not specific to the retweets_of_me method. We do have an issue with
the retweet_count, and we're looking into it. You can follow the issue
here: http://code.google.com/p/twitter-api/issues/detail?id=2141
Arnaud / @rno http://twitter.com/rno
On Wed, Apr 20, 2011 at 5:05 AM,
Hey Jovan,
1) include_entities controls Tweet Entities output (in the status object).
For some User accounts, we're also testing outputting User Entities (for
the description attribute). The include_entities parameter doesn't affect
the output of these User Entities.
2) The Status object
With the follow parameter, you should only get real replies retweets.
If you need to track all mentions, try the track parameter (i.e.
track=@user)
Arnaud / @rno http://twitter.com/rno
On Tue, Apr 19, 2011 at 9:35 PM, Kumar kumar...@gmail.com wrote:
Hi All,
The streaming api documentation
Hey Ali,
Out of band / PIN code authentication is just one of the OAuth
authentication flows we are supporting. Cf
http://dev.twitter.com/pages/auth_overview
If your app can handle the full OAuth process, stick to it and forget about
OOB :)
Arnaud / @rno http://twitter.com/rno
On Wed, Apr
Hey Leo,
We're indeed using Snowflake (a Tweet ID generation service we developed).
Tweets IDs are no longer sequential (but k-sorted with k = 1 second), and
there is no way to count the total number of tweet sent every day.
More info about Snowflake on our Engineering Blog:
Hey Shannon,
Only the list owner can add/remove members to it. If the other account
you're authenticating with is trying to add members to a list he doesn't
own, you'll receive a 403. Take a look to your HTTP body, the error message
is probably You aren't allowed to add members to this list.
Hey there!
There are two ways to identify a list with the new endpoints:
1) With the list_id parameter. For example:
- http://api.twitter.com/1/lists/show.json?list_id=574
2) With the combination of slug AND (owner_id OR owner_screen_name)
parameters. For example:
-
Hey Edward,
You're not getting old :) We removed the RSS link on #newtwitter, but the
exact same content is available through /1/statuses/user_timeline.rss
For example:
http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=rno
Arnaud / @rno http://twitter.com/rno
On Thu, Apr 28,
Hey Luc,
You're not getting rate limited. Let's take a closer look on these two
errors:
1) First error: *Sorry, you are not authorized to see this status*
That means the tweet you're trying to get is protected. Only people
approved by its author (following him) can read / retrieve it.
2) Second
Hey Padma,
This location attribute is specific to geo searches (search API requests
with geocode parameter), and reflects the way tweets are matched:
- It is taking the Geo attribute if the tweet is geotagged.
- Otherwise, it fallbacks to the tweet author's location (as defined in its
profile).
Hey Thomas,
/statuses is not a valid API endpoint, and our routing system assumes
you're trying to reach the statuses account, which is suspended (cf
http://twitter.com/statuses).
Take a look on our timeline resources on http://dev.twitter.com/doc and use
one of these endpoints (for example
Hey tburny,
If you're trying to render the button after the DOM has loaded, the easiest
way is to go for the iFrame version (using query string parameters to
customize its behavior).
More info on http://dev.twitter.com/pages/tweet_button#using-an-iframe
Arnaud / @rno http://twitter.com/rno
Hey Cassiano,
Are you still experiencing this problem? I couldn't reproduce the issue.
Switching access type works fine on my side (for both newly created
existing apps).
Arnaud / @rno http://twitter.com/rno
On Sun, May 1, 2011 at 9:30 AM, BurningFuses cassi...@gmail.com wrote:
Hello. I
query?) through the search
API we can get everything since our last retrieval run, as long as the
number of tweets does not exceed 1500 (Twitter’s maximum number of
results for a query).”
Thanks in advance!
Luc
On Apr 29, 6:36 pm, Arnaud Meunier arn...@twitter.com wrote:
Hey Luc,
You're
Hey Charl,
The doc is outdated, this endpoint indeed requires authentication. Thanks
for reporting, will update the doc.
Arnaud / @rno http://twitter.com/rno
On Sun, May 1, 2011 at 12:02 PM, Charl van Niekerk char...@charlvn.comwrote:
Hi All,
I seem to be having a small issue:
By the way, I was just thinking... Could you double check you're using
http://dev.twitter.com/apps and not any pages at http://twitter.com/apps or
http://twitter.com/oauth_clients ?
Arnaud / @rno http://twitter.com/rno
On Sun, May 1, 2011 at 8:48 PM, Arnaud Meunier arn...@twitter.com wrote
Hey David,
The Tweet Button will share your URL as a t.co link that redirects to the
URL you provide (in your case: t.co -- bit.ly -- final destination). If
you're using the count box, think also to set the counturl parameter to
the final destination. Cf exemple here:
Hey Developers!
You might have noticed that we started updating our developer portal
yesterday, starting with the replacement of the old Twurl console with
Apigee's. If you've never tried Apigee's test console, you should take a
look at it! It's a great tool to test and debug your API calls, and
Hey Dewald,
Neither our TOS nor our Automation Rules Best Practices (
http://support.twitter.com/articles/76915) have changed since the launch
of @twittersuggests experimental feature :)
Arnaud / @rno http://twitter.com/rno
On Thu, May 5, 2011 at 6:00 AM, TjL luo...@gmail.com wrote:
On
Hey Pavithra,
Assuming you're using PHP SimpleXML, you could get the location element
from the google Namespace with something like:
$namespaces = $result-getNameSpaces(true);
$google = $result-children($namespaces['google']);
echo $google-location;
Arnaud / @rno http://twitter.com/rno
On
Hey there,
You shouldn't get this message if you're using the user_id list_id
parameters. Just to be sure, could you please share the full HTTP Request
Response?
Arnaud / @rno http://twitter.com/rno
On Thu, May 5, 2011 at 3:55 PM, Canadaka canad...@gmail.com wrote:
I am having trouble
in advance?
If not, then you may have de facto invalidated that section of your
rules and by implication exempted all developers and applications from
it.
On May 5, 12:45 pm, Arnaud Meunier arn...@twitter.com wrote:
Hey Dewald,
Neither our TOS nor our Automation Rules Best Practices
There is a list of best practices on how to update your Filter Predicates in
the Streaming API doc:
http://dev.twitter.com/pages/streaming_api_concepts#updating-filter-predicates
Arnaud / @rno http://twitter.com/rno
On Fri, May 6, 2011 at 4:54 PM, Shannon Whitley
Thanks for reporting! Will correct this :)
Arnaud / @rno http://twitter.com/rno
On Fri, May 6, 2011 at 11:08 PM, noki noris...@gmail.com wrote:
Hi,
I noticed lists/statuses API end point does not work with count
option but work with per_page option.
The API document(
Hey there,
Could you share the full HTTP Response you're receiving, please? By the way,
did you try to change the text (status parameter)? You could be receiving a
403 because you are trying to send the same status as the last user's one.
Arnaud / @rno http://twitter.com/rno
On Fri, May 6,
Hey Raul,
Could you please give us more details around those two issues (including
Full HTTP Request and Response), and ideally file a new bug on
https://code.google.com/p/twitter-api/issues/list (if you can reproduce the
issue)?
Thanks!
Arnaud / @rno http://twitter.com/rno
On Sat, May 7,
On Mon, May 9, 2011 at 1:21 AM, Faustino Forcén f...@forcen.com wrote:
El 9/5/11 08:01, Arnaud Meunier:
There is a list of best practices on how to update your Filter Predicates
in
the Streaming API doc:
http://dev.twitter.com/pages/streaming_api_concepts#updating-filter-predicates
Hey Balaji,
Which resource were you trying to connect to? As explained in the doc, the
default access level grants you access to statuses/filter (
http://dev.twitter.com/pages/streaming_api_methods/#statuses-filter) and
statuses/sample (
Hey Yama,
- screen_name: I would go for 20 Chars, as it has been the limit for some
time, before we switched to 15 Chars. Some accounts might still have a
screen_name 15 Chars.
- User ID: I would take the safest option and treat them as Status ID (20
Chars or 64 bits INT). So if we decided in
Hey Thiago,
Technically, the limit is account based (each account may create only one
standing connection to the Streaming API). Why would you like to start
multiple connections from the same IP? What is your use case? Remember it is
not allowed to get around limits in statuses/filter (or
. So, creating
multiple connections from the same IP will be a problem in this case?
Regards,
Thiago Souza
On Wed, May 11, 2011 at 13:30, Arnaud Meunier arn...@twitter.com wrote:
Hey Thiago,
Technically, the limit is account based (each account may create only one
standing connection
Hey there,
The Language property (lang) only has effect on the actual Tweet Button. The
Share box language comes from the authenticated user settings (Language
option on twitter.com/settings/account).
Arnaud / @rno http://twitter.com/rno
On Tue, May 10, 2011 at 11:30 AM, max2384
Hey Yahel,
Meet Web Intents: http://dev.twitter.com/pages/intents (take a look on the
intent/tweet intent). It really is super easy to implement. For example:
http://twitter.com/intent/tweet?text=foobar
Arnaud / @rno http://twitter.com/rno
On Tue, May 17, 2011 at 1:18 PM, Yahel Carmon
Hey Mo,
There is already a thread about this subject: http://bit.ly/j2v5Kd :)
I recommend you switch to Web Intents. That's the recommended (and supported
way) to do it. More info on this documentation page:
http://dev.twitter.com/pages/intents
Arnaud / @rno http://twitter.com/rno
On Tue,
Hey Dusty,
The status parameter option has not been removed. It's a bug that has been
filed, but I unfortunately don't have an ETA on a fix. This parameter is
part of the twitter.com website, which is constantly changing. On the API
side, we support Web Intents. That's why I recommended its use
Hey Journey,
There is no dedicated API method to retrieve the most retweeted tweet
in a given time window. However, every status object comes with a
retweet_count attribute that you can for example use to curate the
most retweeted tweets of a timeline, a list...
Hope that helps!
Arnaud / @rno
Hey Max,
That looks pretty extreme! What's your use case? Why would you need to make
that much queries? Are you going to use the Search API or the website? If
you're using the API, Did you consider using the Streaming API
statuses/filter method with the track parameter?
Hey there,
You cannot control Twitter website sessions (i.e. login / logout actions).
OAuth is just an authorization / authentication mechanism to execute API
requests from your app on behalf of a User. You have to handle that logout
feature on your app (i.e. allowing the User to authorize or
Hey there,
If looks like you've hit this bug: http://bit.ly/j1mLSS
If you could capture the exact request you made (+ full HTTP response with
headers) and share this on the issue page linked above, that would help us a
lot.
Thanks!
Arnaud / @rno http://twitter.com/rno
On Wed, May 18, 2011 at
Hey Javier,
We do not support OAuth 2.0 but OAuth 1.0a. If you're looking for a Twitter
/ OAuth 1.0a library, take on look on this page:
https://dev.twitter.com/pages/libraries
Hope that helps!
Arnaud / @rno http://twitter.com/rno
2011/5/19 Javier Solís jso...@tssolutions.co.cr
Hi, i have
Hey everyone,
There have been some great discussions and questions across several threads
and also directly on Twitter. In order to make it simple for you guys to get
answers to your questions, we've just set up a dedicated FAQ page for the
new Application Permission model:
Hey Steven,
I can't reproduce the problem (receiving 5 tweets for page 2). Are you
still having this issue?
Arnaud / @rno http://twitter.com/rno
On Thu, May 19, 2011 at 12:38 PM, StevenBullen stevenbul...@gmail.comwrote:
I am working on a web app and it's been working fine all day, but for
retweets (receiving 3 tweets because the 2 retweets have been
filtered):
https://api.twitter.com/1/statuses/user_timeline.json?screen_name=stevenbullencount=5page=3include_entities=1
Hope that helps!
Arnaud / @rno http://twitter.com/rno
On Thu, May 19, 2011 at 3:00 PM, Arnaud Meunier arn...@twitter.com
Hey there,
Please be careful when you share pieces of code on this Mailing List. I had
to reset your Twitter password because you just shared it publicly. Please
go to http://twitter.com/account/resend_password so we can send you password
reset instructions.
Concerning your issue, the Streaming
1 - 100 of 125 matches
Mail list logo
