I feel like IFTTT is our best bet, while it doesn't do the "Unix pipe" that pipes offered it at least provides some usability to the process.
Yahoo Pipes End-Of-life Announcement
21–30 of 184 posts
Re: Yahoo Pipes End-Of-life Announcement
#22pipes creator here: sad to see pipes shutdown. i am surprised it lasted this long -- it was abandoned years ago. on the positive side, it is nice to see it mentioned in the same sentence as y! maps which used to be a big deal back in the day.
Re: Yahoo Pipes End-Of-life Announcement
#23Re: Yahoo Pipes End-Of-life Announcement
#24Who is working on a pipes replacement and where can I sign-up? Maybe this will be like when google killed Reader and RSS replacements became a hot area...
Re: Yahoo Pipes End-Of-life Announcement
#25Oh man, I use 3 or 4 pipes to filter various RSS feeds. Ugh. Good suggestions for replacements (especially those that don't require my own server) would be much appreciated.
Are they also shutting down YQL? I think YQL queries can do everything pipes can, you just have to write little scripts to do it instead of the UI. Still has the Yahoo problem, but it might be the easiest short term.
Re: Yahoo Pipes End-Of-life Announcement
#26I got about halfway through building a "news blend" app where you tap just the categories you want and it would blend all the latest articles from just your categories into one news feed and email that to you daily. But we never finished it.
Re: Yahoo Pipes End-Of-life Announcement
#27pipes creator here: sad to see pipes shutdown. i am surprised it lasted this long -- it was abandoned years ago. on the positive side, it is nice to see it mentioned in the same sentence as y! maps which used to be a big deal back in the day.
Why did it fail, do you think? I thought it was an outstanding product in terms of both functionality and UI, but it never seemed to gain traction.
For another, Yahoo legal prevented us from doing any kind of long-term storage of RSS feeds. That made the service far less useful than it could have been.
Finally, they didn't give it any resources at all. Management was too preoccupied with the failed Brickhouse project (internal startup incubator) and the host of failed ideas that it spawned.
Re: Yahoo Pipes End-Of-life Announcement
#28I worked on Pipes briefly, shortly after it launched. It was really two distinct products rolled into one. The visual interface was groundbreaking and stunning-I think half my team was hired on the strength of that demo. No one could believe Javascript could do that. The backend was an extremely useful tool for munging RSS feeds. With any kind of support, or even benign neglect, the product would have been successful…
Pipes's interface is primary the work of Jonathan Trevor, with lots of help from Daniel Raffel, Ed Ho and others.
Re: Yahoo Pipes End-Of-life Announcement
#29I worked on Pipes briefly, shortly after it launched. It was really two distinct products rolled into one. The visual interface was groundbreaking and stunning-I think half my team was hired on the strength of that demo. No one could believe Javascript could do that. The backend was an extremely useful tool for munging RSS feeds. With any kind of support, or even benign neglect, the product would have been successful…
I feel like this unique blend will be Yahoo's lasting contribution to the field of management theory.
Re: Yahoo Pipes End-Of-life Announcement
#30Earlier quoted context omitted.
Please suggest alternate. You built a good thing. RSS overall is becoming history.
IFTTT and Zapier are spiritual successors to Pipes, although their focus is on APIs vs feeds. Maybe start a new, open source version of Pipes?
Maybe im dreaming about a free version of Percolate, which I have heard is really cool.