How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/
Slack enables customers to control their encryption keys in enterprise version
91–100 of 178 posts
Re: Slack enables customers to control their encryption keys in enterprise version
#92Earlier quoted context omitted.
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.
2 Options as I see it: Either don't use Slack or try to gather consensus and change things
Re: Slack enables customers to control their encryption keys in enterprise version
#93Earlier quoted context omitted.
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.
Is it not worth Linux running on mainframes because mainframes are expensive? Is it not worth Kerberos being free software because the only real users of Kerberos are enterprises? Computing freedom for anyone is computing freedom, and contributes to a norm of user control instead of service provider control. This step is a very small step, and it only affects a few users. But it's still a step in the right direction.…
Re: Slack enables customers to control their encryption keys in enterprise version
#94Earlier quoted context omitted.
>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. An admin cannot change a user's password. You can enable an account wide feature which allows admins to view all messages but that's separate and costs money. Also not what you described.
If you're using SSO, which almost every big customer does, you can usually do a password reset in the SSO itself. Also I'm pretty sure a Slack admin can change a user's email address, at which point they can trigger a password reset.
Re: Slack enables customers to control their encryption keys in enterprise version
#95How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/
Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?
Re: Slack enables customers to control their encryption keys in enterprise version
#96How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/
Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?
Re: Slack enables customers to control their encryption keys in enterprise version
#97Earlier quoted context omitted.
2 Options as I see it: Either don't use Slack or try to gather consensus and change things
Using Slack isn’t really a choice for most people, but I agree, coming up with alternatives is important.
Re: Slack enables customers to control their encryption keys in enterprise version
#98I see one benefit of this being able to securely throw away data. Like if you are doing work for customer XYZ and chatting about it on the corresponding channel you can throw away the keys for the channel when the project ends.
Wonder how all this granularity works together with the search functionality. Or maybe they maintain per channel search index that can be covered by a separate key.
Re: Slack enables customers to control their encryption keys in enterprise version
#99Earlier quoted context omitted.
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.
Re: Slack enables customers to control their encryption keys in enterprise version
#100How does it compare to Symphony [1]? They want to get the financial market companies, but a lot of them already have their own solution. [1] https://symphony.com/
Can you elaborate on why you are asking how a chatroom service compares to a webapp framework?