|
|
|
|
|
by avh02
1848 days ago
|
|
yeah, was thinking about rebuilding it as OSS just now. the biggest problem is that a security-minded org is going to want control over the server storing their secret messages (otherwise, you're literally giving away which org you are (slackbots get your org id) and your deepest secrets to a third party) to self-host, i think the slash command setup is more complicated/annoying. but i will look in to it again. edit: and you can't really do E2E encryption with slack as a middleman to your API |
|