Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: open
After careful consideration, we have decided to enter into a strategic partnership with PriceGrabber to power the Product Submit functionality of Yahoo! Shopping as of March 11, 2010. As a result of these changes, Yahoo! will no longer provide the Shopping Web Services API, including Shopping Results (the “Yahoo! Shopping Syndication Services”) to you as of March 11, 2010.source [developer.yahoo.net]
This sounds like it's being cut as part of some 3rd party deal without any regard to how existing customers might use it as part of their online store.
Typical, especially from a dying giant desperate for cash.
I have several apps out there that depend on it, and projects in development that also rely on it. All those projects will be scrapped.
And there is nothing 'lazy' about leveraging 3rd party data sources to power your application. Isn't that essentially what a search engine does?
there is nothing 'lazy' about leveraging 3rd party data sources to power your application
It's not Lazy, it's Naive.
It's naive to think the 3rd party tools will remain in operation or free, especially when your business depends on them, which is the case with httpwebwitch, and their business no longer does and they throw you and everyone else that bought into their API under the bus.
I think it's a shame to see it go.
Might've been good to see their deal-making made invisible and non-impactful to websites using that service. What if, as part of the deal, Yahoo and Pricegrabber had integrated on the backend to allow everything to continue working as-is, without major intervention by many developers? I'd imagine there could've been a way to do that.
As it is, I'd bet they'll lose a significant amount of applications using it. I wonder how many companies which were using Yahoo's api let go of developers that built the api integrations during the economic woes of the past couple of years? There might not be anyone left at those companies with the time and know-how to transition to a new api. Once broken, they may opt not to change and just focus on various Google integrations.
This decision has to be coming from microsoft. Why kill that api and not any others?