5 ms·
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
by hackercomplex 11y ago
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 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 cheap than SMS so it seems like it would be in you guy's interest to support webhooks in order to reduce outbound SMS costs.
TLDR; HTTP is the new SMS
- jakejake 11y agoThis 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.
- hackercomplex 11y agoThis kind of thinking reminds me of Twitter in the early days where one founder was trying to pigeonhole it into being for a particular use case. Twitter began it's life as an SMS play also if my memory serves me correctly. 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 ?
- kozkozkoz 11y agoHi, we are working on adding this to our API as webhooks, so you can use the content on your app. For now you can check this: https://dev.gethooksapp.com https://dev.gethooksapp.com