TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Chat as a Service (CAAS) Solutions

1 点作者 jordanbaucke将近 8 年前
We are currently in closed-beta with our Qt&#x2F;C++ based video application. Our users are requesting &quot;text-chat&quot; as a way to communicate with other users.<p>Knowing the litany of &quot;Chat&quot; products that are out there, I&#x27;m not a huge fan of redundancy in communication products. I figure this must be a SaaS that completes my goals. Furthermore, many of these products are &quot;mobile first&quot; (as in they require SMS verification to begin using their service).<p>Things I&#x27;m looking for:<p>- I&#x27;d prefer not to maintain servers<p>- Must have a RESTful API or C++ SDK (we are not developing for Android &#x2F; iOS independently) and we are not building a website (ie. JS SDKs are not very useful)<p>- Ability to add and remove users programmatically when they create accounts on our service.<p>- Security (obviously)<p>- Would prefer not to warehouse messages or be able to access them<p>Things I&#x27;ve looked at:<p>Open Whisper Systems &quot;Signal&quot; Protocol.<p>Pros:<p>- Known standard for secure communications.<p>Cons:<p>- Signal &quot;Text Secure Server&quot; code is unwieldy and poorly documented (https:&#x2F;&#x2F;github.com&#x2F;WhisperSystems&#x2F;Signal-Server)<p>Twilio &quot;Programmable Chat&quot;<p>Pros:<p>- Dynamic REST APIs<p>- 3rd Party hosted (don&#x27;t have any servers to maintain and scale)<p>Cons:<p>- Corporate Service hosting (I know Twilio is better than most)<p>Thoughts?

暂无评论

暂无评论