I've noticed that with the new retweet feature, retweets no longer
appear in the user_timeline API calls. Is this intentional or is this
a bug? If it is a bug, any ideas on the expected fix date? I
noticed a lot of complaints about this searching on twitter (like
"hey, retweets don't show up in
Thanks for the response.
Is there a way to get them without authentication?
On Nov 18, 10:43 am, Marcel Molina wrote:
> They are intentionally removed from the user_timeline.
>
>
>
>
>
> On Wed, Nov 18, 2009 at 9:11 AM, Tyson Lowery wrote:
> > I've noticed t
Venkat,
I'm new at this as well. I tried that code and didn't have much luck,
I decided to go with this code instead which I personally found easier
to work with:
http://wiki.github.com/jmathai/twitter-async
Tyson
On Nov 17, 9:21 am, Venkatesh wrote:
> Hi All,
>
> Am new to twitter and want
Thanks for the response, is there a way to get this data without an
authorization?
On Nov 18, 10:43 am, Marcel Molina wrote:
> They are intentionally removed from the user_timeline.
>
>
>
>
>
> On Wed, Nov 18, 2009 at 9:11 AM, Tyson Lowery wrote:
> > I've n
Let us know what you decide, I know a bunch of apps are waiting to see
what direction this goes in.
Also, I didn't understand this point, "because clients that don't
implement
retweet have the (likely) potential of creating a very confusing
experience for users." Can you elaborate with an example?
Try the Async package to get started, that's what I'm using for OAUTH.
On Nov 20, 7:50 am, Raffi Krikorian wrote:
> oauth is the way to go, and its definitely not in flux. go for it.
> use it. if there is a problem, just let us know.
>
> > I assume there are some nice simple guidelines or pac
Our application has some features available to users who authenticate,
some features for those that do not authenticate. I guess I'll put
this in the authenticate column for the time being.
If it is available publicly on twitter.com, you should allow access to
it via the API without authenticatio
Well this is interesting. If you use statuses/user_timeline and
specify the format as RSS or ATOM, you get the retweets. If you
specify XML or JSON, you do not get the retweets. I don't think the
format should impact the result set.
On Nov 23, 11:24 pm, Abraham Williams <4bra...@gmail.com> wr
They seem to be against this, for reasons that are beyond me.
You also have the problem that if the user hasn't authenticated the
App, there is no possible way to get the retweets.
On Dec 8, 9:41 am, Cameron Kaiser wrote:
> Any thought given to adding an 'enable_rt' argument or somesuch to metho
The decision to leave out retweets is incomprehensible. I don't see
who it benefits to leave these out, besides maybe the programmer at
Twitter who has to do the work to include them. The API Programmers
don't like it, the confused Twitter users who no longer see Retweets
in their favorite third
> >> Or conceivably (though arguably janky) there could be an additional
> >> parameter you provide for the user timeline that opts you in to having
> >> retweets appear. e.g. ?include_retweets=true
Thank you, this is badly needed!!!
On Dec 19, 10:21 pm, Cameron Kaiser wrote:
> > >> Or conceivab
Maybe it is being considered now, check this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/515733c625904ed8/ec71454fcac98781?lnk=gst&q=retweet#ec71454fcac98781
On Dec 22, 9:34 am, Tyson Lowery wrote:
> The decision to leave out retweets is incompreh
Two quick points.
You can't easily fetch those two timelines, unless you have been
authenticated by the user - which is the point of this thread.
Statuses_retweeted_by_me requires authentication.
Also, ironically some applications were broken by the introduction of
Retweets. Retweets used
I noticed this as well. When I did that, I thought maybe that meant
everyone would be grandfathered in, but from reading this thread I do
not think that is the case.
This also makes it difficult for us to troubleshoot this with our
users since we won't know if they have the old token or the new
t
I can't seem to find the difference, does anyone know?
Previous to the new permission system I sent my users to
http://twitter.com/oauth/authenticate/
But for some reason no matter what I do, it says at the bottom This
application will not be able to:
Access your private messages.
So I changed t
w when it is
> released.
>
>
>
>
>
>
>
> On Mon, May 23, 2011 at 3:54 PM, Tyson Lowery wrote:
> > I can't seem to find the difference, does anyone know?
>
> > Previous to the new permission system I sent my users to
> >http://twitter.com/oauth/auth
Is there a way to check whether a user has explicitly granted
permission to their Private Messages?
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-
I think I found the answer from themattharris:
> How do we know what the access level of a user token is?
This is a great idea and one the team has discussed. What we are
going
to do is add a new header to authentication requests that will tell
you the access level of the token you authenticated
18 matches
Mail list logo
