21–30 of 30 posts
Nice work - looks like a cross between IFTTT and Pushbullet. What are your differentiating factors?
Actually we are working on adding Hooks as an IFTTT channel later this month as a trigger so anyone can build their own receipts.
Nice work - looks like a cross between IFTTT and Pushbullet. What are your differentiating factors?
I came here to ask the same thing, sort of. Pushover and Pushbullet both work with IFTTT, and IIRC used to be the only way to get IFTTT to send you mobile push notifications. However, now that IFTTT supports push notifications, why do you still need Pushover or Pushbullet?
Why does this need to be an app? What does it do that a website can't?
We are also working on notifications API for Chrome as the next step for the web interface.
They should call the app "Get Distracted". Its an interesting idea, and potentially very useful, but most likely its going to become the annoying reason your phone keeps going off every 5 minutes. Will give it a try to see.
When I first used it, I got overexcited and configured way too many alerts. But I've been trimming it down heavily, and now a fair percentage of the pushes I get are relevant to me.
Earlier quoted context omitted.
I came here to ask the same thing, sort of. Pushover and Pushbullet both work with IFTTT, and IIRC used to be the only way to get IFTTT to send you mobile push notifications. However, now that IFTTT supports push notifications, why do you still need Pushover or Pushbullet?
This is the first I've heard of Pushbullet, and boy is their marketing frustrating. I just spent 5 minutes trying to answer the question "Is this a service which turns an HTTP POST into an iOS push notification?", only to be greeted with answers like "Bring together your devices, friends, and the things you care about". Argh.
There's a sample curl command right there on the page.
EDIT: Pushbullet's home page has a link to API docs, and it took 30 seconds to find this: https://docs.pushbullet.com/#create-push
I have a feature request: I loved the idea at first glance but then I was appalled to discover that there's nowhere to register a callback URL for any of these events. https://en.wikipedia.org/wiki/Webhook To me it just seems obvious that there should be an either/or option for SMS or HTTP especially since a metric shitton of people are already using slack and hipchat. The transmission costs for HTTP are way more che…
This doesn't strike me as a developer tool (though it could obviously be used by developers). It's for consumers. I don't know of many consumers who want to receive notifications via webhook. If they did do webhooks then you could write one that sent out SMSs though - leave them to do the hard part while cutting them out of the loop! Also I think it's push notifications, not SMS.
Really it's up to the startup.. do they want to try to eventually become the Internet's primary notification propagation channel or are the only interested in catering to a particular mobile phone use case ?
Nice work - looks like a cross between IFTTT and Pushbullet. What are your differentiating factors?
Good question, I love both of this tools, while IFTTT is more about automation, on Hooks we are focusing on notifications only. Our value is the content, it's very easy to create alerts about many things with just one click. Actually we are working on adding Hooks as an IFTTT channel later this month as a trigger so anyone can build their own receipts.
Earlier quoted context omitted.
This is the first I've heard of Pushbullet, and boy is their marketing frustrating. I just spent 5 minutes trying to answer the question "Is this a service which turns an HTTP POST into an iOS push notification?", only to be greeted with answers like "Bring together your devices, friends, and the things you care about". Argh.
In that case you'll like Pushover's home page: https://pushover.net/ There's a sample curl command right there on the page. EDIT: Pushbullet's home page has a link to API docs, and it took 30 seconds to find this: https://docs.pushbullet.com/#create-push
Earlier quoted context omitted.
I came here to ask the same thing, sort of. Pushover and Pushbullet both work with IFTTT, and IIRC used to be the only way to get IFTTT to send you mobile push notifications. However, now that IFTTT supports push notifications, why do you still need Pushover or Pushbullet?
This is the first I've heard of Pushbullet, and boy is their marketing frustrating. I just spent 5 minutes trying to answer the question "Is this a service which turns an HTTP POST into an iOS push notification?", only to be greeted with answers like "Bring together your devices, friends, and the things you care about". Argh.
Earlier quoted context omitted.
When I first used it, I got overexcited and configured way too many alerts. But I've been trimming it down heavily, and now a fair percentage of the pushes I get are relevant to me.
Cool, how long have you been using Hooks for? Actually this happens a lot, our fault for sure, we need to remove some alerts like "TC all content" :)