|
The Rabbi T. White posted:If someone reminds me closer to the time next year, I'll spin up an AWS instance and configure us a private silc (encrypted IRC) server. We have AWS/Google Cloud engineers on staff and free credits for both by extension, and proxy call@sip.yiff.tech to the answer number transparently (same asterisk instance also handles our inbound number). I do not ever want to have to walk rawillkill's dad through ssh.
|
#
¿
Apr 20, 2016 00:31
|
|
|
|
| # ¿ May 15, 2024 00:11 |
|
|
re: slack - We've trialled both Slack and Hipchat (and Mattermost), and I've contributed patches to the ecosystem/API libraries and written bots for both before (and I was also in the Hipchat self hosted server beta/alpha). I have experience with all of them. They do not work well in browsers for this use case, and scrolling performance is murdered if any form of inline previews are enabled. The minimum cost will be ~$1100-$2400/month-ish too. All message/image/inline previews have to be disabled. The desktop client starts pegging 100% cpu after scrolling upward for 15 seconds or so. Keep in mind we fairly often get bursts of 40 msg/sec+, often all links with previews. Scrolling literally drops to < 1 FPS. Slack's free tier has 10k most recent messages; the rest drop off entirely (i.e., you can no longer even scroll upward for them, not just logging history). We use: 561304 2016-04-*.log lines. Reactions to messages do not work because those lines scroll off by the time you click on them. In short, think of this is twitch chat, not business discussions.
|
|
#
¿
Apr 20, 2016 03:38
|
|