Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

emdash.io

Post reply on HN
Print view View original

41–50 of 69 posts

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#41

Post by pz »

cryptonector wrote: post #37

"Individual messages or entire Discussions can be moved after the fact" -- sounds like a start, but I want more. Being able to tag chats with keywords would be nice. Being able to pull chats into docs easily would be nice. Being able to pull chats into more than one doc -- not just move, but tag/reference/copy. Global tags (with ACLs) as well as team and personal tags (also with ACLs) would be fantastic. Don't forget…

> Being able to tag chats with keywords would be nice. Being able to pull chats into docs easily would be nice. Being able to pull chats into more than one doc -- not just move, but tag/reference/copy. Global tags (with ACLs) as well as team and personal tags (also with ACLs) would be fantastic. Don't forget read and access ACLs, not just write ACLs.

Tagging is another organizational feature that is on our roadmap and has always made sense to me. Right now our organizational model is primarily hierarchical which has obvious limitations.

RE: email integration - We have a pretty robust email integration right now. Neville was always insistent that we shouldn't force people into the app to have a conversation, especially for one-off collaborators who get looped into a chat. They can stay blissfully ignorant of the fact that the conversation is actually happening on emdash if it suits them.

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#42

Post by fred_h »

debarshri wrote: post #34

One of the usecases that is relevant for us is supporting other companies over call. Zoom and team are built from meetings but not for support. Key things for support are: 1. Ability to share access to the customers machine with out any hassle and easy acknowledgement for sharing access 2. Recordings and summarirs automatically gets added to tickets and issues 3. Playbooks are handy for the support engineer during th…

Thanks for flagging this use case for us and agree that Zoom/Teams are better suited for presenting vs supporting.

To your specific points:

#1 makes a lot of sense and I sense the "low friction" part of this is the key distinction.

#2 is something we have thought about through the lens of a yet to be built Zapier integration. This would effectively allow you to create more custom methods to route data from emdash into your CRM/other systems of record for customers. Curious if this approach would be interesting.

#3 is in theory supported today. There are several ways you could store/share playbooks for support engineers. For example, you can create a Team and upload the playbooks as shared resources.

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#43

Post by IshKebab »

mtlsnk wrote: post #31

This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.

SSO tax seems like a very reasonable price differentiation method to me. Most of the price increases on sso.tax are quite reasonable for a company that needs SSO (most companies I've worked in don't bother until they are above 100 employees, despite what that site says).

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#44

Post by anilgulecha »

IshKebab wrote: post #43
mtlsnk wrote: post #31

This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.

SSO tax seems like a very reasonable price differentiation method to me. Most of the price increases on sso.tax are quite reasonable for a company that needs SSO (most companies I've worked in don't bother until they are above 100 employees, despite what that site says).

> SSO tax seems like a very reasonable price differentiation method to me

Security is not a differentiation method. It's table stakes for any technical product. That's what the above linked website explains.

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#45

Post by mtlsnk »

IshKebab wrote: post #43
mtlsnk wrote: post #31

This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.

SSO tax seems like a very reasonable price differentiation method to me. Most of the price increases on sso.tax are quite reasonable for a company that needs SSO (most companies I've worked in don't bother until they are above 100 employees, despite what that site says).

There are many small businesses that outsource their IT to managed service providers, but are understandably limited in their budget.

In my opinion, SSO tax results in arbitrary denial of employing best practices for these businesses.

Passwords are evil, because people generally don't care about security or don't have the capacity to employ proper hygiene around passwords. This likely means that SSO tax indirectly contributes to an increased number of account compromises (especially in small businesses, because more limited funds means more limited security; they're low-hanging fruit for bad actors).

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#46

Post by mtlsnk »

wielrls wrote: post #40
mtlsnk wrote: post #31

This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.

To be honest, we're still finalizing our long-term pricing details. For what it's worth, "Sign in with Google" and "Sign in with Microsoft" are available to all users, and we'll prioritize additional canonical OIDC providers as demanded (let us know what you need!). 100% agree with the security benefits here. The SSO reference on our pricing page specifically applies to SAML-based IdPs, intended for customers who req…

I hadn't the time to look around further, so I missed the Google and Microsoft SSO login options. As long as those are/remain free, there is no SSO tax.

I will have another look when I have more time, thank you.

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#48

Post by drewfish »

cryptonector wrote: post #37

"Individual messages or entire Discussions can be moved after the fact" -- sounds like a start, but I want more. Being able to tag chats with keywords would be nice. Being able to pull chats into docs easily would be nice. Being able to pull chats into more than one doc -- not just move, but tag/reference/copy. Global tags (with ACLs) as well as team and personal tags (also with ACLs) would be fantastic. Don't forget…

I was at Yahoo when they did a big email redesign, and the new design didn't work for 1/2 their users. Digging deeper, they found that email users kinda fall into 2 camps: filers and pilers. Filers carefully organize their data so they can quickly navigate to their target. Pilers just collect stuff in a big pile and use search to find their target.

Sounds like you're a filer (I am too). Sounds like emdash is kind of a mix of filing and piling.

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#49

Post by dbmikus »

mtlsnk wrote: post #45
IshKebab wrote: post #43

Earlier quoted context omitted.

SSO tax seems like a very reasonable price differentiation method to me. Most of the price increases on sso.tax are quite reasonable for a company that needs SSO (most companies I've worked in don't bother until they are above 100 employees, despite what that site says).

There are many small businesses that outsource their IT to managed service providers, but are understandably limited in their budget. In my opinion, SSO tax results in arbitrary denial of employing best practices for these businesses. Passwords are evil, because people generally don't care about security or don't have the capacity to employ proper hygiene around passwords. This likely means that SSO tax indirectly co…

The alternative is that the starter pricing tiers are more expensive. Pick your poison.

Re: Show HN: Emdash – Slack/Zoom alternative for distributed team collaboration

#50

Post by cryptonector »

drewfish wrote: post #48
cryptonector wrote: post #37

"Individual messages or entire Discussions can be moved after the fact" -- sounds like a start, but I want more. Being able to tag chats with keywords would be nice. Being able to pull chats into docs easily would be nice. Being able to pull chats into more than one doc -- not just move, but tag/reference/copy. Global tags (with ACLs) as well as team and personal tags (also with ACLs) would be fantastic. Don't forget…

I was at Yahoo when they did a big email redesign, and the new design didn't work for 1/2 their users. Digging deeper, they found that email users kinda fall into 2 camps: filers and pilers. Filers carefully organize their data so they can quickly navigate to their target. Pilers just collect stuff in a big pile and use search to find their target. Sounds like you're a filer (I am too). Sounds like emdash is kind of…

I can't file. I can tag. I can't stand the idea that something belongs in only one box.
Post reply on HN