Despite revamping News, implementing COPPA and letting users share Flickr images directly via mail earlier today, Yahoo announced that it will be shutting down 12 of its products, including AltaVista, Axis, and RSS Alerts among others. The company says that the shutting down of its services is an ongoing effort which will help Yahoo to sharpen its focus and deliver experiences that enhance users’ daily lives. The list goes like this – product followed by their closing dates:
Yahoo! Axis (June 28, 2013): If you installed the browser plug-in, it will no longer work. If you downloaded the app, it will continue to work, but won’t be actively maintained. We encourage you to use the Yahoo! Search app for iOS and Android.
Yahoo! Browser Plus (June 28, 2013): To see all of our current developer offerings, please go here.
Citizen Sports (June 28, 2013): You can still get all the latest sports news on Yahoo! Sports, play fantasy sports like Fantasy Football, and stay up-to-date when you’re on the go with our new Yahoo! Sports app for iOS and Android.
Yahoo! WebPlayer (June 30, 2013): If you’re a publisher and currently using Yahoo! WebPlayer on your site, after June 30 the Yahoo! WebPlayer won’t load. Your users will continue to be able to play media files using native browser support. You may wish to locate and remove the following line in your code:
FoxyTunes (July 1, 2013): To see the latest in the music world, please visit Yahoo! Music.
Yahoo! Neighbors Beta (July 8, 2013): You can visit Yahoo! Local Search to find out what’s going on in your neighborhood.
AltaVista (July 8, 2013): Please visit Yahoo! Search for all of your searching needs.
Yahoo! Stars India (July 25, 2013): To stay up on all your favorite celebrity news, check out Yahoo! India OMG!.
Yahoo! Local API (September 28, 2013): As part of this shutdown, all Yahoo! Local API documentation will also be removed from the Yahoo! Developer Network portal.
Yahoo! Term Extraction API (September 28, 2013): We are eliminating direct access to the Yahoo! Term Extraction API and as of September 28, will require developers to go through YQL. We encourage all existing users of the Term Extraction Legacy API to migrate to YQL requests by September 28. You can use the YQL forums for any questions you might have about migrating to YQL. If you are already using the Term Extraction API via YQL, you don’t need to take any action.