tasn

72 ms·

451.
by tasn 6y ago
Hehe, just did a show HN[1] for Diahook (webhooks as a service) earlier today. I wonder if that's what triggered this posting. :P Anyhow, I wish more people had better webhooks, it's such an important part of any API, so please re
452.
by tasn 6y ago
We are going to start working towards HIPAA soon, and we also going to offer a way to end-to-end encrypt the payload in the very near future. The encryption doesn't help with HIPAA (does it?), but it definitely helps with peace of mind
453.
by tasn 6y ago
We take care of related webhooks channels. We touched on some of them on the landing page, but, in no particular order: Deliverability, monitoring, retries, security (signing), a nice UI for your users to debug, inspect and etc. :)
454.
by tasn 6y ago
Haha, it is self designed (but using bootstrap).
455.
by tasn 6y ago
I'm stealing this interview question, haha. :P Thanks a lot, yeah, there are so many moving parts and pitfalls. I think that what makes it a good question, also makes it a good service (I hope).
456.
by tasn 6y ago
I completely agree. We are still new and we need to earn this over time. Our uptime so far is 100%, but that's easy to achieve as a new company... :) This is something we focus on though, and as part of this focus, we will focus on ear
457.
by tasn 6y ago
Got it!
458.
by tasn 6y ago
We don't do it at the moment, but reach out to me at tom @ the domain, I'd be happy to chat.
459.
by tasn 6y ago
Thanks! Happy to help if I can, feel free to reach out! Email: tom @ the domain.
460.
by tasn 6y ago
Yeah, we also support idempotency (the event ID is used for that). I'll add it to that comment, I forgot to mention it. :P Edit: ahh, I already mentioned it, it's buried in my comment.
461.
by tasn 6y ago
Thanks, I'll keep it in mind when we are ready! I especially like the easy postgres replication. :) I'll reach out about Diahook, as we can also have a self-hosted offering, and I think it could still make sense for you. As you ca
462.
by tasn 6y ago
Will think about reorganising it, thanks!
463.
by tasn 6y ago
Our whole focus is uptime, and I think it's similar to how you use other APIs in your service, how do you deal when you can't reach them? With that being said, this is something we plan on helping with too. We will have retries to
464.
by tasn 6y ago
Zapier does it to an extent, but yeah, it's something to keep in mind. You got my creative juices flowing a bit with this comment, thanks a lot!
465.
by tasn 6y ago
Yeah, I replied to a sibling comment. You are right, I was a bit sloppy with my message. I was just trying to make the point that it was similar to other APIs, and that we take uptime seriously.
466.
by tasn 6y ago
Thanks a lot for your kind words! Please feel free to reach out at tom @ the domain. Happy to help you get started, and I'm super interested in hearing about your other projects!
467.
by tasn 6y ago
I agree, and I think my original comment was a bit sloppy. We already have users that have their own queue system for sending us messages because that's how they deal with similar APIs too. So I definitely see the problem, what I meant
468.
by tasn 6y ago
It's a good point, and actually some of our users already have this local queue implementation anyway because they want to send webhooks asynchronously. So it's definitely something to keep in mind. We already make it easy to quer
469.
by tasn 6y ago
Yeah, you are probably right and the writing is sloppy. I was going to fix it, but I just saw we have an explanation under the pricing boxes. Does that clarify things?
470.
by tasn 6y ago
Your concern is fair, and I wish more companies were as responsible about their user data as you are! I'm actually very privacy conscious myself, which is why we plan on offering optional end-to-end encryption in the very near future.
471.
by tasn 6y ago
Yeah, I know the feeling, haha. It's $1 per 1,000 messages. Retries, or if there's no one to send to are free. So it's just for actual webhooks sent. I'll clarify it now. Anyhow, I'd love to chat and help you get st
472.
by tasn 6y ago
Hahaha yeah, I hope no one ever needs to do it ever again! It's a good question, and I answered it in a sibling comment: https://news.ycombinator.com/item?id=26400510 Essentially I think it's a risk with any exter
473.
by tasn 6y ago
Half of the magic is in the infra (scalability, monitoring, and etc), so we can't deliver the same value with just a library. Though I would love to hear what you have in mind! P.S, what you are doing with Fly.io is super cool!
474.
by tasn 6y ago
I don't think they do, our whole job as an API company is to have uptime (and redundancy for uptime). I think it's the same with every other API company, such as Sendgrid, Twilio and etc. User endpoints on the other hand, fail all
475.
by tasn 6y ago
Haha, yeah, was lucky timing. :)
476.
by tasn 6y ago
Hey everyone, my name is Tom, and I'm excited to be launching Diahook on HN! Diahook makes it easy for developers to send webhooks. Developers make one API call and we take care of deliverability, retries, and offer a great developer e
477.
Show HN: Diahook – Webhooks as a Service(diahook.com)
217 points by tasn 6y ago|106 comments
478.
by tasn 6y ago
I think you and I interpret "premature optimization is the root of all evil" quite differently. To me it doesn't mean you should write slow code, but rather that you shouldn't omptimise a piece of code before: 1. You act
479.
by tasn 6y ago
That's a nice benefit of using async ORMs (not yet available in django), the db calls are explicit!
480.
by tasn 6y ago
I looked at the bottom of https://app.jiga3d.com (the link in the post) and not the main page, that's why I missed it. Thanks!

More ›