Maybe you'll like this new parameter in some timeline methods (ex:
statuses/user_timeline): include_rts=true
Source:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7a4be385ff549ed0/
[quote]
New opt-in API features available today, May 26th: entities, retweets
in
Hi,
In terms of both technicalities and appropriate semantics,
will it be ok to use the attached 'place' to
annotate past or future places, as well as the present location?
This could play a key part in my development, so any help would be
great. Thanks.
On Jun 14, 7:43 pm, Taylor Singletary
we recently (24-48 hours ago) started getting incorrect signature
errors for some of our users. accessing the twitter api with the same
software and the same auth data from a different location works fine.
for one user there were only issues with home_timeline.json but
user_timeline.json worked
To make this slightly clearer Imagine I have retrieved a page with
20 statuses. Status IDs are
60 ... 40
Calling the timeline with max_id=40count=20 allows me to step back in
time. It gives me
40 ... 20
Suppose I just want to see *next* 20 tweets since status_id 60?
I would expect
hi all,
i want to develop symbian c++ application which will send message on
twitter using https request,
if any body have done this plz suggest me path
bye
Hello,
Is it even possible to use abrahams twitteroauth library to get all
the followers the way I want it. I screwed up and now I must rewrite
the cursor idea, Is anybody having a example code for the abrahams
twitteroauth.
Thank you
On 25 jun, 21:50, Sam Wierema samwier...@gmail.com wrote:
On Mon, Jun 28, 2010 at 4:05 AM, Christian Schlimmer
christian.schlim...@googlemail.com wrote:
Maybe you'll like this new parameter in some timeline methods (ex:
statuses/user_timeline): include_rts=true
Thanks for the info, but I can't see how this would be useful to find
retweets of me
From: taylorsinglet...@twitter.com
Date: Mon, 21 Jun 2010 12:10:18 -0700
Subject: Re: [twitter-dev] Statuses getting lost when user is not logged
To: twitter-development-talk@googlegroups.com
This should be fixed soon.. (hopefully today even)
You can follow the bug here.
I know current Twitter Streaming API do not support utf-8 track
keyword.
As an CJK engineer, I hope this feature will implemented so soon.
Does anybody know when will be supported this feature in Twitter
Streaming API??
We don't have current plans to fix this issue. The problem isn't around
utf-8, but rather around non-space separated languages. Our language
processing experts described the effort required, and it's a pretty large
project, and may be computationally impractical in the current streaming
Hello developers,
I'm a new user of OAuth and twitter both :). I need to develop a web
application which is able to authenticate a user using OAuth. What I
want is that the authorization page opens up as a mobile website page
and not like one with a Desktop application. Much like Facebook mobile
Thanks for the tips, Andrew!
Your suggestions to Apple on secret management seems like a great idea.
We'll keep that on our radar.
Taylor
On Fri, Jun 25, 2010 at 2:57 PM, Andrew W. Donoho
andrew.don...@gmail.comwrote:
On Jun 25, 2010, at 15:42 , Taylor Singletary wrote:
However, we'd love
For a desktop application you have one of two options -- use the PIN code
flow in which you still must send the user to a web browser to enter their
credentials, after which the user will be presented with a PIN code that
they must hand-enter into your application. Your other alternative is xAuth,
Are you attaching anything else to the request? 400 bad request usually
implies that there was some kind of error in how the resource was being
accessed. Is there anything different about how you're requesting the home
timeline versus any other resource? Which library are you using?
Taylor
On
Hi all,
I have created a Twitter app using oAuth for authentication.
However, I cannot find any info on how I can retrieve the user's
username in order to get his details. By user, I mean the one that
granted my app permission and for whom the app is making the API calls
Thank you
Hi Thomas,
There are a few ways you retrieve this information. When you are on the
final leg of your OAuth transaction (exchanging a request token for an
access token), part of the response that you get back includes the user id
and screen name for the authenticating user:
Wil: Can you retrieve the signature base string (again, from your current
work) from your library when attempting the call that returns 401? There
must be something minor going amiss there with this parameter for some
reason.
Thanks,
Taylor
On Sat, Jun 26, 2010 at 12:08 PM, John Kalucki
It may have corresponded with a spike of activity on Twitter -- our current
authentication implementation has some unfortunate side effects when
stressed, and one of them is to return spurious 401s.
Are you still seeing the issue?
On Sat, Jun 26, 2010 at 11:39 AM, Udi udi@gmail.com wrote:
Hi Taylor,
Ok. Here's the entire thing:
Generated base string:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce
%3Dmvzi5szav5dciif4%26oauth_signature_method%3DHMAC-
Ah wait, I ran a couple more tests just to be sure and the signatures
match the sent sniffed one guess I missed something previously...
Base:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
Taylor Singletary wrote:
We're waiting on a few minor bug fixes to be in place before rolling this
out to a wider audience. I'll post a new message when things are good to go
and we're ready to accept applications into the feature.
Any update or ETA on this? I have an app that I'm eager to
The answer is soon! :) We hope to roll this out more widely this week.
On Mon, Jun 28, 2010 at 7:56 AM, Decklin Foster deck...@red-bean.comwrote:
Taylor Singletary wrote:
We're waiting on a few minor bug fixes to be in place before rolling this
out to a wider audience. I'll post a new
What's the deal with search? It's not returning all the data. Just
look at any of the trending topics for instance. The Status site
hasn't been updated.
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a couple more tests just to be sure and the signatures
match the sent sniffed one guess I missed something previously...
Base:
Great! Let me know if you still need assistance.
Taylor
On Mon, Jun 28, 2010 at 8:10 AM, Wil willi...@gmail.com wrote:
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a couple more tests
Oh wait, it does include them I just missed it.
So much for premature celebration...
On Jun 28, 11:10 pm, Wil willi...@gmail.com wrote:
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a
Let's start from a common point. By using the same inputs, we can try and
meet in the middle with exactly the same signature, signature base string,
and authorization header.
Using the following values:
Consumer Key: TwitterConsumerKey
Consumer Secret: TwitterConsumerSecret
Access Token:
Can you provide more details? We aren't seeing this behaviour. Search has
never returned all of the data and in periods of high volume will not index
every single tweet. If you want every tweet on a topic we highly suggest
the streaming interface.
Jonathan
@jreichhold
On Mon, Jun 28, 2010 at
Excellent Taylor
Thanks a lot
I was going crazy with this
On 28 Ιούν, 17:19, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Thomas,
There are a few ways you retrieve this information. When you are on the
final leg of your OAuth transaction (exchanging a request token for an
Hi,
I got exactly the same values:
Base string:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DTwitterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1277739588%26oauth_token
Hello there,
I'm speaking on behalf of a third-party Brazilian site that wishes to use
OAuth, I ask you these following questions:
1. The site is a Get more Followers kind. In the past had been some issues
using OAuth, so the site discontinued that.
2. Is there any problem for this kind of service
It looks like it is working again now. My test was as follows:
1) Go to http://search.twitter.com, click on the top trending topic.
2) Look at the 15 results returned. Usually they all say half a
minute ago or less than a minute ago
In my test, it said 3 minutes ago, 5 minutes ago, 9 minutes
Hi again,
I made a real request this time because in the previous one, I
couldn't control the nonce and timestamp generation directly so I copy-
pasted the code it used and modified it a bit. This is the real
generated data which has a non-mock nonce and timestamp.
Timestamp: 1277742686
Nonce:
Hi Wil,
Did some more tests. Why are you passing source in this context? I don't
recall this being an operator for the Streaming API. If you're passing it as
some kind of analogue to a source parameter you'd pass in basic auth on
tweet creation, it's unnecessary here unless there's some other use
Hi Emerson,
OAuth doesn't change any of our policies related to this area. Our policies
on get more followers kind of sites is expressed here:
http://help.twitter.com/entries/68916-following-rules-and-best-practices and
here: http://help.twitter.com/forums/26257/entries/18311
Taylor
2010/6/28
Hi Taylor,
Finally! It now works. TweetSharp includes the source parameter by
default on all requests (I think). Thus, I overrode the
TwitterClientInfo just for that request and cleared out the
ClientName field. Now it works!
I guess on your side, the code filters out unknown parameters before
hello guys,
I am using twitter API to get the information about
users.However, there are some limit dor call rewuest of 150 request
per hour.how can I increase API call rate limit?.. Thank you
Quoting John Kalucki j...@twitter.com:
We don't have current plans to fix this issue. The problem isn't around
utf-8, but rather around non-space separated languages. Our language
processing experts described the effort required, and it's a pretty large
project, and may be computationally
Hi there
150 requests per hour is the limit for Basic Authentication-based
requests, with OAuth-authenticated requests allowed further requests.
Normally it's 350 (and is due to be raised to 1,500 per hour at some
stage), however given the extra load Twitter's under during the World
Cup OAuth
Try calling without the count parameter. The page and count parameters
may not work properly with since_id, and since_id may not work
properly if the id you pass results in too many tweets. :/
On Jun 27, 3:17 am, Terence Eden terence.e...@gmail.com wrote:
To make this slightly clearer
Wil,
Fantastic. So glad you got it working, and thanks for sharing the solution
which worked for you.
Matt
On Mon, Jun 28, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
Hi Taylor,
Finally! It now works. TweetSharp includes the source parameter by
default on all requests (I think). Thus,
41 matches
Mail list logo
