Show HN: Sameroom.io
We wanted an easy way to connect #channels/rooms between different chat teams, so we made Sameroom. It's like plumbing for chat—allowing you to connect different services in interesting ways (e.g. Hipchat <=> Slack, Flowdock <=> IRC, Slack <=> Slack). Would love to hear what you all think about it.
34 comments
[ 1.7 ms ] story [ 99.8 ms ] threadDo all the chat messages pipe through your servers? How is privacy protected?
The great thing about Sameroom is it doesn't store anything! It's just a broker.
- there is support for services other than Slack (and more coming)
- no webhooks are involved, you just click some buttons and it's on
So once we do, our main concern is how to keep it legal. Because clearly, the functionality would be really great for a lot of use cases.
One possible thing to consider: Have a public chat room on the homepage connecting some sample chat rooms. Allow users to jump to the rooms in different services.
Do you plan to offer one / is that possible?
Our goal is to be the plumbing that connects other apps/services. We think the main value here is the possibility to use whatever app/service you like best to communicate with other teams.
I can see this being especially useful as a support chat for a company or open source project or ... where you have one chat room that can be connected by all the different chat platforms so you don't have multiple places to monitor.
1. when you kick the mentor or vendor out of your main room, they no longer have a record of what happened. Since Sameroom replicates messages across channels, everyone has a copy (like with email)
2. If your mentor or vendor wants to involve someone else from their side, it's not easy (they have to ask you to send an invite). With Sameroom they would control access on their end of the discussion.
3. Your invitee is forced to use Slack, which isn't ideal if they normally use another tool, say HipChat. Even if they already use Slack, they have to switch teams, which... well, it doesn't seem to scale very well.