41–50 of 97 posts
Pipes where awesome! The product seemed to have influenced a few products (off the top of my head): 1. IBM's Node Red [1] 2. AWS IoT Things Graph [2] I'm sure there are others? [1] https://nodered.org/ [2] https://aws.amazon.com/iot-things-graph/?nc=sn&loc=3&dn=6
https://docs.microsoft.com/en-us/azure/azure-functions/funct...
Thanks for posting and the nice comments. Glad to have built something that people found useful...
It used a weird mix of free services, including Yahoo Pipes and IFTTT. It went from email to RSS to Google Calendar to SMS. It was nice while it lasted, but now Google Calendar doesn't send SMS notifications so it's no longer possible for free.
Thanks for posting and the nice comments. Glad to have built something that people found useful...
Thanks for posting and the nice comments. Glad to have built something that people found useful...
Pipes where awesome! The product seemed to have influenced a few products (off the top of my head): 1. IBM's Node Red [1] 2. AWS IoT Things Graph [2] I'm sure there are others? [1] https://nodered.org/ [2] https://aws.amazon.com/iot-things-graph/?nc=sn&loc=3&dn=6
I remember not too many years ago (2011/12?) Yahoo was the best source of free APIs for weather/stock/news information. It was well documented, fully-featured, had a great web dashboard, and most importantly of all it was super stable. Not sure if it shut down or if it just became irrelevant in the modern web. But many a engineering student plugged into it to make "hello world" weather apps.
Most stock tracking APIs require licenses to use, or have terrible latency. Similar with weather APIs now.
Source: I was the Service Engineer on pipes for around a year or so.
1) When you went to the pipes landing page, there were a few demo pipes to show people what was possible. One of them combined search results from say ebay/craiglist/amazon to show prices for things.
One day I was looking through the source of these, and noticed there were affiliate ids in the ebay/amazon links. They all belonged to some early team member who had long since left.
I showed a couple people on the team, we all guessed at how much they were making from this, said good on em and went about our day. I still wonder how much they ended up making from it.
2) It was my first on-call, and all of a sudden the west coast pipes cluster just went bananas. After ~5 minutes, east coast started to go nuts and the west coast subsided.
Someone, despite numerous defensive measures, had found a way to create a pipe-bomb that would recursively call multiple versions of itself. Once the west coast load balancer failed over, one of these requests would hit the east coast and the 'virus' would jump over there. This flipped flopped back and forth until I figured out how to blacklist pipe ids (and eventually got a code fix).