troygoode

Hey we're launch buddies. :-) Congrats on the launch!

Thanks Hana! I hope you and your team are doing well!

Yes, we definitely consolidate (and normalize) state for deliverability, opens, and clicks across providers and channels.

One interesting thing we do here is for channels like Slack & Teams that support webhook-based click interactions natively: we offer you a webhook proxy so clicking the "Approve" button on the Slack notification will hit Courier first (so we can count it as a "click") before proxying through to your approval handler.

All of that data is then normalized in our logs, which you can view in our UI or have streamed to your systems via webhook.

Great point! I just changed it to a reset code (to make it a bit terser than a full URL just for the sake of brevity).

That is a really good point. We should probably turn this into a 2FA code example instead.

Edit: fixed!

Did IoT really fizzle out though? In my mind it just became more mainstream expected. Yes, silly things like connected refrigerators / toasters / whatever were a gimmick but the watch I'm wearing, the earphones I'm wearing, the scale on my bathroom floor, the blood pressure cuff under my sink – so many of the things I use each day are now connected (sometimes indirectly) to the Internet and it really is just "normal."

(I do think the 3D printing craze was premature given the state of the tech then and now. I did just see a video of 3D printed full-size boat though so who knows...)

100%. I'm old enough that when I started my career we were still storing credit card numbers on our servers (and many companies were unfortunately doing so in the raw...). PCI compliance luckily knocked some sense into the industry. Crazy to me that some people don't realize that PII and secrets like passwords are basically in the same category now.

FWIW given GDPR, CCPA, et al so do auth & communication. I'd honestly have a big problem with our team wanting to store passwords ourselves...

Sure, it is obviously biased – I started Courier because I think developers shouldn't be building their notifications infra themselves.

Why would you offload payments instead of e.g. connecting directly to payment gateways yourself, but wouldn't do the same for auth & notifications?

He specifically addresses this in footnote [3].

This is incorrect. HN is run by Y Combinator; yes, PG started YC, but he retired from YC 7 years ago.

For a more modern take on Obsidian Portal I strongly recommend LegendKeeper (https://www.legendkeeper.com/). I use it for the campaign I DM for both for my own notes and for making some of the lore / locations / characters easily accessible for the players.

This is definitely an area of B2B sales that often gets overlooked; glad to see innovation in this space! Great looking product, too.

Congrats on the seed round!

Got it dang. Understood.

> I would love to see if there are more startups or products out there like MagicBell

We don't currently do in-app notifications so not directly like MagicBell, but handle a lot of the other challenges you mentioned. We were heavily inspired by how Slack solves this problem (they're one of our investors):

https://www.courier.com/

Sorry we missed that! Will get it added ASAP.

Edit: Docs are updated and change is deploying now. Thanks for the heads up Hana!

Update! We love this idea here at Courier (https://www.courier.com/) and just launched a MagicBell integration (https://docs.courier.com/docs/magicbell) to make it easy to send notifications to email via SendGrid/SES/Mailgun/etc., SMS via Twilio/MessageBird/Plivo/etc., mobile push, Slack, MS Teams, and – now – in-app!

Looking forward to finding other cool ways to work together.

Hey Hana – I love what you're doing with in-app. Congrats on YC!

Courier (https://www.courier.com) is also in this space, but we're focused on other channels like email, Slack, SMS, MS Teams, SMS, etc. as well as handling orchestration capabilities around lists, preferences, and sequences. I'm pretty confident you & I started Magicbell & Courier for the same reason: we were both tired of seeing this have to be built over and over.

Glad to see the space is heating up!

Great feedback! We're starting to work on our recipient UI very soon. FYI you _can_ filter the logs page by recipient already, though that isn't as convenient for sure.

If you like SendWithUs (which the company has pivoted away from in favor of their new product, Dyspatch), I think you'd love the templating system we've built:

https://www.courier.com

Hey Rob, we (www.courier.com) sit on top of your existing email provider(s) – Mailgun in your case – and help make common email and notification tasks easy:

- visual template builder

- automatic retries

- switching between service providers (permanently or for failover)

If you implemented Mixpanel via Segment, we can also ingest those events directly from Segment into Courier (or you can call our API directly).

We'll be releasing automations early next year to help make the advanced drip stuff easy – but we aren't there quite yet.

Why would Theranos count? They were not YC.

You can. Feel free to deploy it to your device. You just can't distribute it.

I don't disagree with your point (it is pretty interesting!) but I do think 2008 – one year after the iPhone was introduced – is a bit of a special scenario for Apple that isn't broadly applicable to other stocks/downturns.

You should talk to the guys at Wasmer: https://wasmer.io/

It isn't a jab specifically at Quora, it's a jab at what the entire market looked like before Stack Overflow came along – namely their arch-nemesis at the time: Experts Exchange.

> Tesla will speed up or slow down and change lanes automatically.

You are still required to engage the turn signal; Tesla will speed up / slow down to execute the merge, eventually, and will steer the merge for you but does not make the decision to do so autonomously (though it'll recommend a new lane to you with a blue lane line on your dash).

React Native gives you the best of both

FWIW while I don't think it would actually happen, yes, Apple could "buy" Google. When companies merge the expectation is that the resulting combined entity will equal the two companies combined market caps.

Take theoretical company (Company A) worth $100MM and with a single shareholder (Shareholder A) who owns 100% of the 10MM shares of stock. They "buy" Company B which is also worth $100MM and has a single shareholder (Shareholder B) who owns 100% of Company B's 10MM shares. Company A executes this by issuing 10MM _new_ shares in Company A that will now be owned by Shareholder B. Company A now has 20MM shares and is worth $200MM because it has added Company B's assets, income, etc.

Of course in practice it frequently goes terribly wrong (ref: Microsoft & Nokia, Verizon & Yahoo, many others) and I don't think Google would actually have much incentive to go along with this. Just saying it COULD be done if both companies truly believed the outcome would be favorable.

You’re assuming rural Americans actually own the food and energy they produce.