3 ms·

Cool project, I think this might be a possible replacement for IFTTT for example depending on the ease of building plugins, but would be good to have that kind

by srcr 12y ago

Cool project, I think this might be a possible replacement for IFTTT for example depending on the ease of building plugins, but would be good to have that kind of automation under your own control.

jnbiche 12y ago
Actually, wit.ai would do very well to partner with IFTTT or Zapier to make a recipe or whatever they call their plugins. It'd be a good match.
- ar7hur 12y ago
  Wit.ai team here. We've been thinking about it actually, and webhooks as well. Stay tuned!
kevinbowman 12y ago
I use a local install of Node-RED [0] instead of IFTTT, I find it really good for ad-hoc wiring together of stimuli / physical responses (eg I have some LIFX bulbs). [0] http://nodered.org/ http://nodered.org/
- tmuir 12y ago
  I don't understand why Node-RED hasn't blown up on HN yet. Its ridiculous how powerful it is for connecting hardware, web APIs, websockets, HTTP Servers, twitter, push notifications, shell scripts, you name it. Additionally, it runs on PC, Mac, Beaglebone Black, Raspberry Pi, and Arduino. For instance, I'm working on a flow that passes a hardcoded Google Maps url to page2image.com, gets back a screen shot, runs a python script to analyze the image for the traffic level, and makes a determination based upon a predefined threshold. If there is high traffic, a pushbullet notification is sent to my phone. If there is low traffic, a text message is sent to my phone. I have each notification set to a different sound. On my Android, I'm using Tasker to sense when I enter a gps radius, and then send a message through no-ip to my beaglebone running Node-RED to kick off the whole process. The end result should be that during my morning commute, when I'm approaching a particularly congested area, I'll get one of two sounds on my phone. One sound indicates that I should take the main road, and the other sound indicates that I should take side roads.
  - spoonfoe 12y ago
    This is awesome.

by srcr 12y ago

Cool project, I think this might be a possible replacement for IFTTT for example depending on the ease of building plugins, but would be good to have that kind of automation under your own control.

jnbiche 12y ago

Actually, wit.ai would do very well to partner with IFTTT or Zapier to make a recipe or whatever they call their plugins. It'd be a good match.

ar7hur 12y ago
Wit.ai team here. We've been thinking about it actually, and webhooks as well. Stay tuned!

kevinbowman 12y ago

I use a local install of Node-RED [0] instead of IFTTT, I find it really good for ad-hoc wiring together of stimuli / physical responses (eg I have some LIFX bulbs). [0] http://nodered.org/ http://nodered.org/

tmuir 12y ago
I don't understand why Node-RED hasn't blown up on HN yet. Its ridiculous how powerful it is for connecting hardware, web APIs, websockets, HTTP Servers, twitter, push notifications, shell scripts, you name it. Additionally, it runs on PC, Mac, Beaglebone Black, Raspberry Pi, and Arduino. For instance, I'm working on a flow that passes a hardcoded Google Maps url to page2image.com, gets back a screen shot, runs a python script to analyze the image for the traffic level, and makes a determination based upon a predefined threshold. If there is high traffic, a pushbullet notification is sent to my phone. If there is low traffic, a text message is sent to my phone. I have each notification set to a different sound. On my Android, I'm using Tasker to sense when I enter a gps radius, and then send a message through no-ip to my beaglebone running Node-RED to kick off the whole process. The end result should be that during my morning commute, when I'm approaching a particularly congested area, I'll get one of two sounds on my phone. One sound indicates that I should take the main road, and the other sound indicates that I should take side roads.
- spoonfoe 12y ago
  This is awesome.