[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Just to throw my 2 cents in. Without a reasonable replacement for mobile devices, we'll likely remove it, and I'm expecting a substantial backlash from UberTwitter users. It does look like it would be relatively simple to roll-your own with the streaming api, which makes me wonder why this is being removed. I don't have metrics on how many of my users access this endpoint, but I can say that in the past year when there were issues with it, we would get plenty of feedback. People like to use it to randomly find interesting people. If sounds like the twitter folks are re-considering, I hope so. -Paul On Mar 5, 10:39 pm, Raffi Krikorian ra...@twitter.com wrote: hi all. i just wanted to let you know that we've heard all the issues around this deprecation and potential removal of public_statuses -- we're currently reviewing and thinking this over and will have more to say next week. thanks for your patience. fixed. BTW, it doesn't look like the docs on the apiwiki have been updated with the deprecation notice. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
BTW, it doesn't look like the docs on the apiwiki have been updated with the deprecation notice.
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
fixed. On Fri, Mar 5, 2010 at 6:10 AM, earth2marsh ma...@earth2marsh.com wrote: BTW, it doesn't look like the docs on the apiwiki have been updated with the deprecation notice. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
hi all. i just wanted to let you know that we've heard all the issues around this deprecation and potential removal of public_statuses -- we're currently reviewing and thinking this over and will have more to say next week. thanks for your patience. fixed. BTW, it doesn't look like the docs on the apiwiki have been updated with the deprecation notice. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
especially considering how surprisingly complex this endpoint is to maintain. On Wed, Mar 3, 2010 at 9:06 PM, Abraham Williams 4bra...@gmail.com wrote: One less method for Twitter to maintain when the data is available through the Streaming API. Abraham On Wed, Mar 3, 2010 at 20:21, Patrick Kennedy kenned...@gmail.com wrote: Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Is there a reasonable replacement to provide the same functionality in mobile apps? -- Hwee-Boon On Mar 5, 12:04 am, Raffi Krikorian ra...@twitter.com wrote: sorry - its being deprecated as of today. it is being removed on 5 april 2010. hope that clears up the confusion. On Thu, Mar 4, 2010 at 6:54 AM, Brian Smith br...@briansmith.org wrote: Ryan Sarver wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Just to be perfectly clear: is it being deprecated or disabled on that date? Thanks, Brian -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Quite I am surprised to see this go, I'm not going to start using a streaming API on a mobile device so I'll have to remove that functionality from the app I guess. Seems like a shame, although I've no idea of the metrics of how many of my users check it. On Mar 4, 4:44 pm, Hwee-Boon Yar hweeb...@gmail.com wrote: Is there a reasonable replacement to provide the same functionality in mobile apps? -- Hwee-Boon On Mar 5, 12:04 am, Raffi Krikorian ra...@twitter.com wrote: sorry - its being deprecated as of today. it is being removed on 5 april 2010. hope that clears up the confusion. On Thu, Mar 4, 2010 at 6:54 AM, Brian Smith br...@briansmith.org wrote: Ryan Sarver wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Just to be perfectly clear: is it being deprecated or disabled on that date? Thanks, Brian -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
What is the replacement for this endpoint for mobile applications? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Yah, the public_timeline was awesome back in the really early days of twitter when volume was really low and you could actually keep up. Since then its a vestige of the original Twitter API that doesn't really work anymore because you can't see all tweets with it. It's just a limited random number of tweets so it doesn't make it very useful. The only advantages of the public_timeline is that its a simple get that doesn't required auth and it's cacheable between users locally (since it doesn't change very often). If you doing server to server access with the API, it shouldn't be an issue to switch. Even though I can't think of anything off the top of my head that API would be useful for these days for desktop and mobile clients, there may be something innovative that it may useful, which for those clients it kind of sucks. Since the streaming API doesn't support OAuth/XAuth yet like the other APIs and like was said at the dev meet up is not really targeting connections directly from the desktop/mobile clients connections right now, the developers using that API are going to need to host a server in order to replicate that functionality. It wouldn't be difficult to roll your own server to replicate the public_timeline with data from the spritzer if you had too, but some mobile and desktop developers hitting the Twitter API directly may not be in a position to host their own servers for their own clients. Part of me says that it would be wise to wait until general xAuth is up and running for everyone (for those that need to login without going through the web) and is working on the streaming API and the streaming API is ready for connections directly from clients. However the other half of me thinks that that since the public_timeline sucks that it should just die either way. Zac Bowling @zbowling On Thu, Mar 4, 2010 at 9:22 AM, Carlos carlosju...@gmail.com wrote: What is the replacement for this endpoint for mobile applications? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
One less method for Twitter to maintain when the data is available through the Streaming API. Abraham On Wed, Mar 3, 2010 at 20:21, Patrick Kennedy kenned...@gmail.com wrote: Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Ops. Was thinking about user_timeline v. home_timeline. So, public_timeline is now going away too. On Thu, Mar 4, 2010 at 12:06 PM, Abraham Williams 4bra...@gmail.com wrote: One less method for Twitter to maintain when the data is available through the Streaming API. Abraham On Wed, Mar 3, 2010 at 20:21, Patrick Kennedy kenned...@gmail.com wrote: Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
