ceruleanscott

4 ms·

1.
by ceruleanscott 8y ago
Slack showcases the HIPAA logo on their security page, but upon closer inspection - https://slack.com/terms-of-service/supplement#healthcare - you'll see that unless you've signed a separate agreement with th
2.
by ceruleanscott 8y ago
We think integrations can be great, and offer a few of our own right now (a proof-of-concept /weather command and a deeper integration with Global Relay for some of our fintech customers, for example). That being said, we're bein
3.
by ceruleanscott 8y ago
Shameless self-promotion: We (Trillian) just received HITRUST certification, provide a BAA, and offer both a SaaS variant and the self-hosted Trillian Server product, both of which run over our own open IM protocol. We're not exactly
4.
by ceruleanscott 13y ago
Because this isn't a new project for us; if it was, we'd absolutely be using XMPP. Our choices were to dump 10+ years of engineering and spend another two trying to wrangle XMPP to fit our needs (and do so across Windows, Mac, iO
5.
by ceruleanscott 13y ago
Yeah, inertia. What we've tried to do with IMPP is to roll all of the features that IM users actually want into the core protocol versus just saying "it's open!" or "it can be extended!" and hoping someone els
6.
by ceruleanscott 13y ago
A few notes: 1) We are obviously aware of XMPP, having been developing client-side interfaces to it for years. 2) We started this project in 2001 - around the same time Jabber was in its infancy - and as smacktoward notes, the main reason w