papercups

The best language for the task at hand, when presented with time constraints, is the one that you already know well. OP said in the article that they authored Papercups [1]. Adopting Elixir for a websocket-push service makes a lot of sense, then. However, why don't you learn Elixir, some OTP, and then reconsider that question? You could be missing out. [1] https://github.com/papercups-io/papercups

Sure thing. Mattermost and most open source chat tools not Google searchable. They can offer public communities but unless they are rendering static version of the site it is really not SEO friendly. They are very enterprise/security focused so if you want something secure and private Mattermost is fantastic. We started out making Slack and Discord Google searchable and search engine friendly see: kotlin for example https://slack-chats.kotlinlang.org/ they have around 50,000 pages indexed by Google. We render a static version for Google while giving you the real time experience of a chat app. Secondly most large communities end up being a community support channel. So for anyone with customer support experience having your conversation in one place is really crucial as well as some sort of open close state. I was also the author for https

No affiliation, but have you looked at https://papercups.io/ ? They are also OSS: https://github.com/papercups-io/papercups

Shameless plug here if anyone is interested in an open source live chat tool check out https://github.com/papercups-io/papercups I m one of the maintainers :)

I know a lot of open source project maintainers. Most of the sponsorships are negligible. The ones that have a bit more sponsorships tend to offer some sort of priority support. But even that is very difficult. I also maintain an open source project with 4k stars but we didn’t even bother with the sponsorship path and decided to monetize by charging for a hosted version. For reference https://github.com/papercups-io/papercups

Client side: React - Typescript Backend: Phoneix - Elixir We're a live message tool and it is basically what Elixir is built for https://github.com/papercups-io/papercups. The Elixir community has been great and incredibly friendly. I originally was worried about the size of the community but that hasn't been an issue the community has been super helpful. I also think the annual stackoverflow usage surveys are very misleading because most of the community's questions get asked in ElixirForum and not on Stackoverflow. Phoneix is the web framework of Elixir which is very similar to Rails but minus a lot of the magic has been very helpful for our productivity as well. If I had to built another service that is websocket heavy I would definitely use Elixir. Even if it was a standard crud app I would still most likely choose Elixir.

We're pretty similar to Chatwoot in some ways - Kam described some differences here: https://news.ycombinator.com/item?id=26503697 To reiterate some of the differences, or why people might choose us at the moment: - A lot of our users really like our Slack integration. For small teams, this means they don't even really have to use our dashboard if they don't want to, because they can do everything from Slack. [0] - We offer a live screen sharing feature [1] - We're working on a library to offer complete customization of the chat UI on your website [2] [0] (We need to set up a better recent demo video of our Slack integration, but if you skim our changelog you'll probably get the gist: https://github.com/papercups-io/papercups/blob/master/CHANGE...) [1] https://storytime.papercups.io/ [2] https://github.com/papercups-io/chat-builder

Yeah I agree, we're planning on updating the landing page to include a lot more screenshots/videos/demos :) In the meantime, here are some screenshots from our GitHub wiki: https://github.com/papercups-io/papercups/wiki/Features And our demo page: https://app.papercups.io/demo

Interestingly, the features page goes straight to github. With a list of features... followed by screenshots. So I found it! https://github.com/papercups-io/papercups/wiki/Features

Thanks for building this! Love this version I think this would work great for making and fixing bugs. I think automated tests and chores as a category would actually be great to add to this. For our open source project (https://github.com/papercups-io/papercups). We participated in hacktoberfest recently and one problem we ran into is people submitting low quality PRs. Which ends up taking up way more time to review than to merge. I would love to be able to filter by users who have merged multiple issues or some sort of quality bar for our bounties. Obviously since you are just starting out your users won't have too many issues merged. You might be able to work around this by finding the number of Github issues an author have merged previously to any projects that is greater than x number of stars. This way you might be able to bootstrap