[twitter-dev] Re: New opt-in API features available today, May 26th: entities, retweets in timelines, custom oauth_callback schemes
Thank you for fixing the issue of retweets not being included in timeline data! I reported the issue as soon as it arose, when the retweet feature was first introduced, and have been monitoring the situation ever since: http://code.google.com/p/twitter-api/issues/detail?id=1312
[twitter-dev] Re: How to retrieve url link written in a tweet please?
Example of C# code for ASP.NET: new Regex(@https?://([-\w\.]+)+(:\d+)?(/([\w/_\.]*(\?\S+)?)?)?).Match (tweetText) I strongly reccomend the open source Linq2Twitter library for obtaining data from Twitter in .NET applications. I use LInq2Twitter to put my tweets on my personal homepage:- http://www.timacheson.com/#twitter The server-side approach has several advantages, e.g. it will be indexed by Google and can be seamlessly cached by the built-in caching in ASP.NET for optimal performance.
[twitter-dev] Re: How to retrieve url link written in a tweet please?
If you want to do this with pure JavaScript, I strongly reccomend following this complete tutorial:- http://www.jamessenior.com/post/Building-Twitter-Search-using-the-ASPNET-Ajax-Library-Beta-e28093-Part-1.aspx
[twitter-dev] Unable to get complete timeline for a user (including retweets) without logging-in! New API method urgently required.
Problem: There is an important limitation in the API regarding retweets. With the new retweets feature, in the current API, it is not possible to get a complete timeline for a user (unless you have the user's password). This is bad. Firstly, it means user timelines retrieved from the API will always be potentially incomplete, with retweets excluded. Yet retweets are considered part of a users timeline and always have been. Secondly, it means I can't retrieve my own complete timeline without logging in, which is surely an unnecessary extra step. The API functionality for retweets seems inconsistent with other API methods, notably statuses/user_timeline which does not require a log- in. It's also inconsistent with the RSS feed which does include retweets in a users' timeline. Solution: A new API method is required, to retrieve retweets for a user without logging in. DOCUMENTATION statuses/user_timeline Returns the 20 most recent statuses posted from the authenticating user. It's also possible to request another user's timeline via the id parameter. This is the equivalent of the Web /user page for your own user, or the profile page for a third party. Note: For backwards compatibility reasons, retweets are stripped out of the user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and Atom). If you'd like them included, you can merge them in from statuses retweeted_by_me. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline
[twitter-dev] Re: Getting retweets in user timelines
I strongly agree with the OP. Problem: Unable to get the complete timeline for a user including retweets (without logging in)! There is an important limitation with the API regarding retweets. With the new retweets feature, in the current API, it is not possible to get a complete timeline for a user (unless you have the user's password). This is bad. Firstly, it means user timelines retrieved from the API will always be potentially incomplete, with retweets excluded. Yet retweets are considered part of a users timeline and always have been. Secondly, it means I can't retrieve my own complete timeline without logging in, which is surely an unnecessary extra step. The API functionality for retweets seems inconsistent with other API methods, notably statuses/user_timeline which does not require a log- in. It's also inconsistent with the RSS feed which does include retweets in a users' timeline. Solution: A new API method is required, to retrieve retweets for a user without logging in. DOCUMENTATION statuses/user_timeline Returns the 20 most recent statuses posted from the authenticating user. It's also possible to request another user's timeline via the id parameter. This is the equivalent of the Web /user page for your own user, or the profile page for a third party. Note: For backwards compatibility reasons, retweets are stripped out of the user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and Atom). If you'd like them included, you can merge them in from statuses retweeted_by_me. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline
[twitter-dev] Re: Retweets and the Public Timeline
I strongly agree with the OP. Problem: Unable to get the complete timeline for a user including retweets (without logging in)! There is an important limitation with the API regarding retweets. With the new retweets feature, in the current API, it is not possible to get a complete timeline for a user (unless you have the user's password). This is bad. Firstly, it means user timelines retrieved from the API will always be potentially incomplete, with retweets excluded. Yet retweets are considered part of a users timeline and always have been. Secondly, it means I can't retrieve my own complete timeline without logging in, which is surely an unnecessary extra step. The API functionality for retweets seems inconsistent with other API methods, notably statuses/user_timeline which does not require a log- in. It's also inconsistent with the RSS feed which does include retweets in a users' timeline. Solution: A new API method is required, to retrieve retweets for a user without logging in. DOCUMENTATION statuses/user_timeline Returns the 20 most recent statuses posted from the authenticating user. It's also possible to request another user's timeline via the id parameter. This is the equivalent of the Web /user page for your own user, or the profile page for a third party. Note: For backwards compatibility reasons, retweets are stripped out of the user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and Atom). If you'd like them included, you can merge them in from statuses retweeted_by_me. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline
