I'm building an IFTTT platform/service for nano. It's working but I'd like some feedback before I decide to launch anything.
**UPDATE: I GOT IT WORKING "NANO FAST" NOW. THIS IS GOING TO BE AWESOME!!!!**
I run a Principal Representative node and have been wanting to do something with it for some time. Work has been slow for me so I decided to just start making something fun and came up with building an IFTTT platform for nano. I've spent the last 3 days working on it and I worked out most of the kinks, and it works! (**see update**) ~~But... I'm disappointed by one thing in particular. IFTTT is too slow to showcase nano, don't get me wrong it works and it's kinda cool but every test / action is delayed. I'm trying to figure out if it's me doing something wrong on IFTTT but I'm worried it's always going to have a bit of a delay. Either way, my~~ main question is would you REALISTICALLY use this service? In order to publish it for everyone, there's a $200/year fee which I'm willing to spend if you think there's a good use-case for it. I'd just hate to put all this effort and money into something that will not be used.
For those who are unfamiliar with IFTTT (If This Then That) it's a easy drag and drop tool that allows you to connect multiple services (APIs) and create your own custom applet. For example with my trigger you could do: \` If you send 0.1 nano to this address, light up a thank you sign (using WeMo smart plug or something else) \`
My initial use cases were so people could make fun hacks (similar to the bird feeder) without needing to run a node, use rpc, websockets, etc. but I'd love to hear some ideas on how you would personally use it. The idea is the IFTTT trigger will take a nano address and a min amount required to trigger the other action, I won't be creating or storing any keys or personal info.
Right now I've purchased the domain [nano.lol](http://nano.lol) (can't believe it was available!) and renamed my node (previously [node.nanoart.io](https://node.nanoart.io)) Which I hope to (eventually) keep building into a more robust webhook service...