Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?
Can you clarify? They both offer chatrooms and depending on your definition of webapp framework they both are as well (external app integration, bots...).
It's pretty clear many customers don't want control, they want features, and irc lacks those.
Not true, Slack is actually pretty far behind on terms of features. It is true that people like the better looking, easier to use technology however.
IRC doesn't even have the only feature I care about: the native ability to see messages sent while I was logged out.
And no, I don't want to run my own bouncer, and I don't want people running their own insecure bouncers across my company. Yes, I could use something like IRCCloud but that requires another account and I'm tied to their client unless I pay[1]
The title of this post makes it sound like a bad thing, but in regulated industries like Finance,
firms are required to produce chat transcripts of the traders to regulators. Slack would be unusable in this industry if the firms could not capture all of the chat logs.
This is a good thing for computing freedom: it puts more control in the hands of customers instead of requiring them to outsource encryption to Slack. It's a small step, since it's Amazon KMS and since presumably Slack still sees cleartext in transit. But it goes in the direction of restoring the security profile that a customer did when they ran their own internal IRC server, and that's a good thing.
The article says it’s only open to enterprise customers. Computing freedom you have to pay a ton for is not really freedom. It’s really not even close to the control of IRC.
It’s still their product. You have the freedom to not pay for it and use whatever alternative you want or build your own.
Not true, Slack is actually pretty far behind on terms of features. It is true that people like the better looking, easier to use technology however.
IRC doesn't even have the only feature I care about: the native ability to see messages sent while I was logged out. And no, I don't want to run my own bouncer, and I don't want people running their own insecure bouncers across my company. Yes, I could use something like IRCCloud but that requires another account and I'm tied to their client unless I pay[1] https://www.irccloud.com/faq#faq-bnc
There are a few web clients that use redis to allow you to see history. I will be the first to admit, those clients don't scale as well as IRC itself does. [1] [2] And of course, someone would have to manage that infrastructure. It isn't for everyone.
Another option would be to rent a really cheap VM and run a tmux or screen session with weechat [3] or epic [4], but command line isn't for everyone either.
Reads more like "Hands over control to any customer that will pay for it." [1] I wonder if the UI shows the employees that their employers have the keys. [1] Edit: as opposed to only regulated customers. Also, there's an upcharge...you don't automatically get control.
Are you saying you had some sort of presumption of privacy on a corporate Slack account? If you did, you had it in error. If I am reading this right, this actually reduces your exposure as an employee. Instead of your employer and Slack having full access to everything you do on that account, now your employer has full access but Slack's access is reduced substantially. (If the setup is working as I expect, Slack wil…
Perhaps not in the U.S., but Europeans could definitely sue their employer if private messages are read (which Slack explicitly supports).
Slack is a shady thing and I'll never install their desktop app, which presumably is full of user tracking.
Isn't this just shifting partly your trust from Slack to Amazon?
I think it's very smart of Slack. AWS Encryption SDK[1] is a well designed, battle tested data encryption library. Amazon KMS is a well audited service used by AWS to manage all sorts of keys and even supports external HSM integration. For slack to build all this from the ground up would be time consuming. Hard part being 3rd party validation, penetration testing and certification. [1]: https://docs.aws.amazon.com/en…
Amazon isn't perfect, but I sure as hell trust Amazon KMS more than most others out there.
I am not sure slack can ever meaningfully become encrypted while having persistence. All it takes is for a admin (or hacked admin account) to change the password of the target slack user and login as said user to view all their private messages. The encryption is mostly pointless as far as I can tell when all of it is circumvented by a changed password.
I wonder if just using standard OTR over slack for sensitive stuff is viable.
Reads more like "Hands over control to any customer that will pay for it." [1] I wonder if the UI shows the employees that their employers have the keys. [1] Edit: as opposed to only regulated customers. Also, there's an upcharge...you don't automatically get control.
Most acceptable use policies (or information security policy or employee handbook) point out that employees must presume that the company does monitoring of the employee's communications.
Further, some readings of the ECPA (Electronic Communications Privacy Act) indicate an obligation on the part of the company to monitor.