Show HN: An open source alternative to some of Slack AI's premium features
https://github.com/meetbryce/open-source-slack-ai
The official Slack AI product looks great, but with limited access and add-on pricing, I decided to open-source the version I built. Especially for all the communities on Slack that would have to convert to paid and buy the upgrade to access the official SlackAI product/add-on which is not going to be financially viable in most cases.There's no plan to sell anything, just something I built as a way to learn some new tools that I thought others might get use out of.
The repo is a ready-to-run slack app that provides thread summaries and channel overviews on demand using OpenAI (heavy lifting done by gpt-3.5-turbo and a touch of gpt-4) and some standard NLP analysis. Anyone technical could easily swap in Claude or Ollama (and i'd welcome the pull request, it's been on my to do list!).
There's a link in the readme to a blog post I wrote sharing more about the how/why if you're interested.
I'm a product manager by day, so it's been fun to do some real coding again.
(
21 comments
| 19 points
| on HN
)
Perhaps I'm lacking context but I couldn't figure out your question and I'd like to help you find an answer!
[0] https://book.keybase.io/chat
Is this one Open Source too? I wasn't sure which project it was under. But if it is then maybe someone else can revive it because I'd love to have a Slack alternative that is E2EE.
While digging up supporting links, I was reminded that Element exists from the creators of the Matrix protocol, and while their website is an MBA-buzzword-athon their communities page does cite E2EE <https://element.io/communities#:~:text=secured%20with%20end-...> and they are permissively licensed https://github.com/orgs/element-hq/repositories
I mean there's lots of open source stuff. Signal is open source and people still complain about it being centralized but just won't run their own servers and connect them together. So I think open source isn't enough. It takes people working on things.
I think this is the most impressive part!
i better fix that
That said, the Slack API limits third party apps from accessing chat history of private messages, so any implementations like this are artificially limited. In addition, if you're hosting something for your company to use, it would realistically need to take into account user permissions to make sure the AI isn't sending them data they shouldn't have access to. That could be tricky to implement correctly.
oh wow. i should have guessed taking it off the pricing page meant the price went up, not down.
this works in private channels, but not in DMs. i think that's okay given the likelihood of things getting to much for manual parsing in a 1:1 context.
if you've got the time/inclination, I'm interested to hear more about what you're getting at with the permissions & access piece