Laura, you rock!
Thanks! Super excited to make this public.
Open Source at IFTTT
21–29 of 29 posts
Re: Open Source at IFTTT
#22I hadn't heard of Jot before. Looks really interesting and useful for a bunch of applications.
Re: Open Source at IFTTT
#23Laura, you rock!
Getting to work alongside Laura is one of the highlights of being at IFTTT.
Re: Open Source at IFTTT
#24I am in love with IFTTT's Do apps. The UX is purely phenomenon and has become part of my daily life. I hope they keep up these types of projects!
I have been meaning to dive in. What are some recipes/use cases that worked out best for you?
I use it to email notes to myself. This recipe is one of the top killer features of my Apple Watch, as it means I always have a GTD input device available within about ten seconds.
Re: Open Source at IFTTT
#25jot should be jottt. Keep up the good work!
+1
Re: Open Source at IFTTT
#26Earlier quoted context omitted.
How does this handle authenticated requests? For example, does it store OAuth tokens and refresh on your behalf?
The Maker Channel Action doesn't support authenticated requests, at least anything beyond something you could send in the URL or body of the message. We do this to prevent people from using it to spoof requests to public authenticated services that might view such behavior as slightly "shady". The Maker Channel is really meant for prototyping and experimenting and so we've limited the capabilities to keep the uses in…
That's somewhat of a bummer, as it also forces all legitimate users to leave their endpoints acessible for everyone who knows the URL.
Have you thought about at least adding support for authentication where the credentials are generated by IFTTT? (Similar to the "secret" that you use for the trigger) This would allow makers to protect their endpoints while still disallowing spoofed requests.
Re: Open Source at IFTTT
#27Earlier quoted context omitted.
If you haven't looked recently, they now have incoming and outgoing web requests: https://ifttt.com/maker
But no authentication? Makes it somewhat useless. How many services allow unauthenticated requests?
There's a secret key. Isn't the idea that you're wiring this up to your own services?
Re: Open Source at IFTTT
#28To me, that looks around 99% Mac/Apple-centric, and that puts my interest firmly at zero.
Touché that their open-source efforts can't actually be used on true open-source systems like Linux.
I like IFTTT, but this was massively underwhelming.
Re: Open Source at IFTTT
#29Earlier quoted context omitted.
How does this handle authenticated requests? For example, does it store OAuth tokens and refresh on your behalf?
The Maker Channel Action doesn't support authenticated requests, at least anything beyond something you could send in the URL or body of the message. We do this to prevent people from using it to spoof requests to public authenticated services that might view such behavior as slightly "shady". The Maker Channel is really meant for prototyping and experimenting and so we've limited the capabilities to keep the uses in…
Why not make it a paid service then? I'd pay a couple dollars a month to have this ability, and you'd raise the bottom line for spammers.