1. 33
  1. 12

    Yahoo Pipes was a lot of fun. A highlight of the Web 2.0 “mash-up” era. I remember making a little homepage that pulled posts from a half-dozen different sources. Does anyone what happened to Pipes after Yahoo shut it down? Has there been a Pipes revival somewhere?

    1. 4

      Isn’t that https://ifttt.com/ ?

      1. 9
        1. 4

          It’s been many years since I used IFTTT, but last I checked it was vastly simpler. You can’t do complex pipelines like the one shown here - it really is “if (this), then (that)” and you can’t chain them together.

          I didn’t know about Yahoo Pipes while it was still up so I never got a chance to use it, but AFAICT the closest thing I’ve seen to it so far is Huginn.

          1. 2

            Huginn looks amazing! This could really help with a lot of work stuff where IFTTT just doesn’t have the flexibility or programmability that I need. Thanks!

        2. 3

          Along with huginn, riko is also on my list to try: pull-based and no web GUI, but self-contained with native RSS/Atom.

        3. 8

          I used it a lot during its prime to generate a uniform RSS of web comics from their respective individual feeds. To this day I haven’t found an alternative that’s equally easy to use.

          1. 7

            I remember “tarpipe” from the same era, and remember it fondly. I even posted about it at the time: tarpipe.com - Programming 2.0? (post includes screenshot of tarpipe). I seem to remember that Yahoo Pipes had more features (e.g. the loop mechanism as mentioned in this thread’s post) but tarpipe was still magical.

            1. 1

              Wow, I don’t think I saw tarpipe before. Always love to fill in gaps in my historical understanding. Thanks for the link!

            2. 6

              What a throwback, I remember that you could publish pipes so others could modify them, I was using a pipe in ~2011 to get an RSS feed for new pirated releases of a given TV show on thepiratebay, that my torrent client would consume to download them automatically, and I was able to simply “fork” and fix the pipe when it broke.

              1. 6

                I’m laughing some this morning seeing this. I worked with the author on this project back then. In a lot of ways, we were using it very similarly to the new generation of Headless CMS products that exist now. The business people could publish content using whatever tool they wanted and it was automatically piped into the company’s public-facing website.

                1. 4

                  I had a twitter bot retweeting a certain hashtag which was build completely as a yahoo pipe. Really cool stuff