turnly VS laudspeaker

Have you tried using something designed for the job? Like this? https://github.com/turnly/turnly

👋 Hi, everyone, maintainer here. As we prepare for Turnly's initial release, I want to introduce some fantastic features that will bring us close to being a viable alternative to existing QMS. TLDR; → Turnly at GitHub Turn 0.3.6 comes with fantastic new APIs and other unique features! ☑️ Support for multiple locations (branches) ☑️ Web-based widgets for ticket-taking ☑️ Customizable branding ☑️ Custom Data Fields to gather initial information ☑️ Integration with Twilio for turn notification And more! We'd love you to try Turnly and share your valuable feedback, and together, we can make it better 🙏

What are some of the differences between LimeJourney and Laudspeaker https://github.com/laudspeaker/laudspeaker or mautic https://github.com/mautic/mautic?

Been working on our startup laudspeaker (an alternative to firebase cloud messaging) [1] as well as trying to write more! I like science fiction thrillers similar to what michael crichton used to write and have been working on a story called Panopticon around encryption, spycraft, and three letter agencies [2]

[1] https://laudspeaker.com/ , https://github.com/laudspeaker/laudspeaker

No congratulations is necessary the Laudspeaker project (https://github.com/laudspeaker/laudspeaker) is doing perfectly fine.

$75/mo is not particularly expensive, Braze's starter plan is close to $35k/year

we switched from a redis backed queue (bullmq) to rabbit at our company (https://github.com/laudspeaker/laudspeaker) when we hit speed issues . We found bull had a much lower throughput, after a lot of tuning compared even to rabbit out of the box.

Oh yea the titles are a little off, since they're pulling off of the original comment and not the repo itself. The Laudspeaker description came from:

"Apart from working on my start up, and open source project https://github.com/laudspeaker/laudspeaker (open source firebase cloud messaging) I've been writing a short sci fi story, sort of like a techno thriller inspired by michael crichton, called Panopticon."

https://news.ycombinator.com/item?id=41348190

Apart from working on my start up, and open source project https://github.com/laudspeaker/laudspeaker (open source firebase cloud messaging) I've been writing a short sci fi story, sort of like a techno thriller inspired by michael crichton, called Panopticon. Its set in our time frame and is all about encryption, three letter agencies, and a race against time! Here's a link with the first 20 pages if anyone is interested! https://docs.google.com/document/d/1VRI4X5fCUpwurUDvKmvzJpT7...

https://news.ycombinator.com/item?id=39836316

Laudspeaker | Remote| Full Time | Senior Software Eng / Founding Eng

We posted on hacker news a few days ago - you can see the whole post here (https://news.ycombinator.com/item?id=39836316)

Summary below:

We are building a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker

We are a small team of 3, had a successful launch on HN a year ago, are backed by YC, and and are now starting to close large companies deploying our software to touch millions of users.

Who You Are:

Our mission is to build a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker and our site here: https://app.laudspeaker.com/login

We had a successful launch on HN a year ago, and have moved quickly since and are now starting to close large companies deploying our software to touch millions of users.

We continue to have an ambitious roadmap and are looking for a founding senior engineer to radically improve the product (take it from a 1->10, we have already built the 0->1) and help "level-up" the founders. We need our product to scale to tens of millions of messages sent an hour, handle millions of incoming api requests, add introduce engineering best practices, and tooling for our product to maintain SLAs

The right engineer will be excited to join a small team, excited to work on open source software, works well autonomously, can deal with ambiguity, and wants to work remotely (with minimum 4 hours of overlap sometime between 8am - 8pm pst)

Some more details:

- We work in Typescript with Nest.js for the backend and react for the frontend

laudspeaker: https://github.com/laudspeaker/laudspeaker