Live data from Hacker News

Yahoo Pipes End-Of-life Announcement

pipes.yqlblog.net

51–60 of 184 posts

Re: Yahoo Pipes End-Of-life Announcement

#51
post #6

pipes 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.

Thanks so much for you and your team's work on Pipes - I'd be lying if I said it didn't inspire many parts of Zapier!

Re: Yahoo Pipes End-Of-life Announcement

#52
post #6

pipes 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.

Pipes has long been a sort of monument to the faith of a bygone age -- the first flush of Web 2.0 optimism, when standard formats and open APIs were going to let us mix and match and mash up services of all kinds at will.

That faith is dead now, of course, scoured from the earth by walled gardens and VC money. But like Catholics in Elizabethan England, some of us quietly tend our secret shrines and pray for its return.

(Hopefully that will work out better for us than it did for them.)

Re: Yahoo Pipes End-Of-life Announcement

#53

Who 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...

We're working on something that covers a lot of the same ground, although it's not exactly the same thing. It's also not very polished right now, but we definitely hope to get to that level eventually. It's all open source, Apache Licensed, and built using Grails. We don't have YQL, but we extract entities from the content and store it in a triplestore that can be queried using SPARQL, and eventually the SPARQL support will be woven more completely through things.

https://github.com/fogbeam/Neddick

Re: Yahoo Pipes End-Of-life Announcement

#54
post #51
post #6

pipes 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.

Thanks so much for you and your team's work on Pipes - I'd be lying if I said it didn't inspire many parts of Zapier!

Same here... Pipes has been an inspiration to use with a lot of the stuff we've been doing as well.

Re: Yahoo Pipes End-Of-life Announcement

#55

I 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 wrote a simple Wordpress plugin that works with RSS feeds. In addition to aggregating fees, Pipes has been a go-to solution when people report feeds that are malformed, have some weird characters or anything that chokes the Wordpress RSS parser (simplepie). People would run them through pipes, which seemed to handle anything and output clean RSS.

I'm sad to see it go and it'll be missed by quite a few people who use my plugin.

Re: Yahoo Pipes End-Of-life Announcement

#57
post #30
post #15

Earlier quoted context omitted.

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?

It really would be oh so nice to have something that can ingest RSS and Tweets and then apply filters to them while visualizing the logic through a graphical interface. Maybe even some fuzzy machine learning to use in building filters. Some more advanced dupe technology would go a long way. People would be building their own techmemes in no time. You could build ranking systems that award bonus points if something li…

This is exactly what we are doing at http://www.feedsapi.com , we don't use a graphical UI for the logic but keywords and RegEx to create filters... Many folks are already building their own techmeme with our API, it's however not a free service. I'm not sure if this fully fits your requirements but you should take a look.

Re: Yahoo Pipes End-Of-life Announcement

#58
post #6

pipes 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.

Please suggest alternate. You built a good thing. RSS overall is becoming history.

Check out http://www.feedsapi.com , we do almost everything with rss feeds...

Re: Yahoo Pipes End-Of-life Announcement

#59

Pipes was the first service I ever owned from an ops perspective (circa 2008). We had two clusters, one on each coast. I thought we had capacity to take one offline to do a full upgrade, turns out we didn't. By the time I turned the west coast back online, the east coast was failing health checks, and the LB failed everything over to the west coast, which then proceeded to be overloaded, and everything flipped back t…

Business model :)

Just to be clear, I had not idea about that until now.

Re: Yahoo Pipes End-Of-life Announcement

#60
post #35

Earlier quoted context omitted.

Have you tried IFTTT? Not sure what your usecase is, but that might do the job.

IFTTT doesn't let me basically reformat an RSS feed and then see it in my RSS reader. Most/all of my use of pipes was "go scrape this thing and turn it into RSS, filtering out stuff I don't want to see." It was great for that - I'm unaware of anything that is even trying to replace it.

THIS is exactly what http://www.feedsapi.com does, it's a paid service with a 2 weeks free trial.
Post reply on HN