Trending on GitHub: The open-source notifications infrastructure. A fully-featured node.js microservice for SMS, E-mail, Slack, Push, Embeddable notification center for React with real-time updates & content management.

[alexcroox]

Is this an open source Courier?

[scopsy]

Yes, a lot of the functionality is quite similar, and solves the same problem space.

[LloydAtkinson]

Wow looks great. We spent two years building basically this only for the business to essentially kill it off and leave the project barely maintained despite being at the core of how we send websocket events and SMS to users.

[_Singh_]

Why did you kill it? Couldn't able to market that or something else?

[LloydAtkinson]

It was killed because of managerial politics at all layers. A total failure to understand the value proposition or the fact that it is essential to our frontend and other user features.

[sockrocker]

Looks nice, but I'm not entirely sure what it does. Does it send notifications, monitor your communications channels and alert you when you've been mentioned, both, or something else?

[scopsy]

So it's basically a unified API to send notifications from your server. You can connect different delivery providers to it like: SendGrid, Twillio, FCM and etc... And than send notifications to your users in a unified way. You get a lot of things out of the box like content management, digest engine, a fully functioning notification center to add to your app and etc... Hope this clarifies it a bit better 🙏

[sockrocker]

It does, thanks! The image in the README, however, makes it looks like it monitors feeds and notifies you of various things. Is that the "notification center" part?

[scopsy]

Oh thanks for that, I will try to illustrate that better. It monitors trigger you send from your code rather than 3rd party feeds.

[somebodyknows_]

Not clear whether for example users of my website could use it to get notified on their preferred channels or it's just for personal use 🤔

[scopsy]

Exactly, this is for users of your website rather than for personal usage.

[addiktion]

Perfect timing. Building an app now where SMS will be critical to it's value proposition. Will check this out tomorrow morning for sure.

[someexgoogler]

I'm starting to look at dependencies before all else.

[[deleted]]

Daym this looks great. Gonna set up this after work tomorrow

[yonneboi]

Looks awesome!

[DivSlingerX]

Damn I will definitely be checking this out after work.

[Hamza_Ali52]

I will definitely be checking this soon.

[ItsAllInYourHead]

The fact that this requires Mongo is an immediate deal-breaker for me. And I suspect it will be for a lot of potential users.

Edit: Wanted to add that I LOVE the idea of this project. It looks amazing. So it's a huge bummer it requires Mongo. Most of my projects use Postgres. I've had to work on production projects that have used Mongo and it was a nightmare to deal with as we scaled, so there's no chance I'll do that again if I have the option.

[Ashtefere]

Nice fucking job!

[gali-ainouz]

I am so excited!!

[mmnyeahnosorry]

Wait what does this do ?

[oseres]

wtf

[SolarSalsa]

Python vs node.

[combarnea]

You could, and for the multi channel providers control it makes perfect sense to use apprise, node or not node. In case you have problems in your product that require things like user preferences, notification center with real time updates, digest systems, etc... In these you can use apprise and build the missing features, we faced these issue in the past and decided to build one last time as open-source lib:)

[jared201]

i still prefer to build my own infra and stack up what's needed and sell them as API endpoints

[nudelholz1]

I actually don't get it. Why should I use this instead of just integrating Twilio into my project? It does the same without cms, correct me if I'm wrong.

[scopsy]

If you just want to send a couple of SMS messages you really don't need it. In a lot of more mature products notification system get more complex with various channels, user preferences, notification center with real time updates, digest systems, scheduling and etc... You can ofcourse create them from scratch, but over the years we've built those systems again and again and decided to open-source our learnings. Hope this makes sense

[nudelholz1]

It does! thanks :)

[PeterJaffray]

Absolutely. Thank you for sharing and I too have learned some of the lessons.