4 ms·
Both of the technologies you named as examples are free and open. Anyone can inspect them and deploy them on their own. Slack isn’t like that unfortunately. Thi
by femiagbabiaka 8y ago
Both of the technologies you named as examples are free and open. Anyone can inspect them and deploy them on their own. Slack isn’t like that unfortunately. This is a move to add another feature that will attract enterprise customers, I would doubt that even Slack themselves would proclaim this as a move towards greater software freedom.
- pmart123 8y agoI agree that this move is articulating enterprise customer demands rather than demonstrating greater software freedom. I don’t view this as unfortunate though. Slack is a productivity and collaboration product versus a utility like a low level database or encryption method. As such, many users and businesses want to pay for support, added features, hosting/availability/backups. It is better to have someone having to pay Slack a lot for power features than have a bunch of targeted ads in Slack. The buck stops somewhere.
- Zancarius 8y ago> Anyone can inspect them and deploy them on their own That's what I don't get from reading this thread. Like you said, Kerberos does have its uses outside enterprise deployments, and if you want authenticated/encrypted NFS for whatever reason it's really one of your only options.