For the most part I experience none of the issues you mention. I get pinged when my name is @'d or on some emergency channels where I have it set to ping me on any message. I find it massively more useful and less distracting than IM+Email.
The one notification challenge I do have with it is that channels can move quickly enough that if I get @'d more than once while I'm afk for a bit it's easy for me to to respond to the latest ping I got but not catch earlier ones. I'd really like it to have a separate view that summarizes your mentions.
As for the features you don't understand:
- Email doesn't give you search for conversations you weren't a part of to begin with. That's the huge upside of a transparent-by-default tool like Slack when it comes to search. I can search for "Solr latency" and find conversations I wasn't a part of, from a time I may not have even been an employee. That's huge.
- File transfers - same, see above for email. Corp Lan shares rarely get search/indexing right.
Oh and FWIW I'm at least 70% curmudgeonly neckbeard too :)
<snip> We also reserve the right to terminate your account (or the access privileges of any end user) and this TOS at any time for any reason, or no reason, with or without notice. Upon termination of your account, we will have no obligation to maintain or provide Your Data, and will delete or destroy all copies of Your Data in our possession or control, in a reasonably expedient way, unless legally prohibited. </snip>
Data retention is a separate issue, but I can envision reasons why I'd want to reserve a maximally "We don't owe it to you" clause, as a SaaS operator. (Slack, for example, allows arbitrary file uploads. This is a high risk feature, for a lot of reasons, data security, copyright compliance, and explosive reputational risk being only three of them.)
As a separate matter: if these clauses discomfit you, speak to enterprise sales. For $10,000+ you can negotiate better ones. If you do not wish to pay $10,000+, that's fine, but you don't get custom legal language.
For a free account this might well work.
For a paid account, a unilateral-termination right, if not worded properly, could kill all the legal protections of the terms of service by turning the TOS into an "illusory contract." [1] The SaaS provider could lose its limitations of liability, choice-of-law and choice-of-forum clause, arbitration provision, etc.
A better approach might be to provide that the SaaS provider can temporarily suspend the account for good reason, and perhaps enumerate some example reasons. That could be coupled with a termination for cause clause (with termination following notice and an opportunity to cure except in egregious cases).
Usual disclaimer: I'm not your lawyer, this isn't legal advice, YMMV, small differences in fact can make big differences in outcome, check with your own lawyer before making decisions, etc., etc.
[1] http://en.wikipedia.org/wiki/Illusory_promise. For more information and citations, see http://www.oncontracts.com/using-wordpress-coms-terms-of-ser... (self-cite).
That sounds right --- the key difference is the refund, which wasn't mentioned in Patrick's original post.
If termination is for cause, you might not have to give a refund (although it'd look better to outsiders, and thus be more defensible in court, if you did give a refund).
How do you word this correctly to still be able to terminate whenever you want?
(I know one should speak to a lawyer, and I'm not running a SaaS business, I'm just curious of the generics)
Of course, conversely, as the person receiving service, you absolutely want the provider to have binding obligations -- and "we can cancel this at any time for any reason or no reason with no obligation to give you anything, including your data, afterwards" isn't what you want from a service you are relying on in any kind of business use.
> As a separate matter: if these clauses discomfit you, speak to enterprise sales.
Or just don't use the service that offers them. The reason services use boilerplate like this isn't that its essential, its that the perceived cost/benefit ratio warrants it because most people don't read TOS and don't change behavior based on them.
While email can be used for group communication, it's not ideal for the typical, constant interactions of a small team. Let's consider one use case. In email, file sharing with an individual is a multi-step process (new message, select recipient, insert subject, add attachment, write comments, send). In slack, you click upload, select file, and it's sent. No formality or friction in creating a new thread, selecting recipients, ad infinitum. Not to mention, it's hard to discover all the files shared between you and a group of people via email. This is important in an organization. A similar argument could be made for search and group messaging.
This snap judgement is the equivalent of suggesting that you'd forgo wearing gloves in the winter because wrapping warm pieces of fabric around your hands serves the same purpose. Purpose ≠ efficiency.
p.s. the desktop app > keeping a tab constantly open :)
That's not so much a feature of "using email" as "the UX of a typical general-purpose email client". But, heck, the UX of sharing-via-email from even a typical Android app is somewhat more streamlined than what you present, and the same is true of many desktop apps that have email distribution as a feature. The recieving side is still a problem, though the kind of progress in email clients we've seen with -- just to look at gmail as an example -- schema-based actions and Inbox's workflow -- suggests that we may not be too far from the time when the recieve workflow for document-sharing-via-email is improved, after a fairly long period where email client workflows were fairly static.
<groupname>.irc.slack.com
Google the internets for username & password setup.
yep: https://slack.zendesk.com/hc/en-us/articles/201727913-Connec...
Isn't that an horrific end-run around corporate security? or does irc.slack.com provide IP address whitelisting to restrict connections to those from within the company? Client SSL cert checking?
It just seems like a remarkable focal point that could give access to a lot of sensitive corporate data.
I've had the same experience as you with Slack and Hipchat. The front end guys with the shiny tools love it, and I live with it.
To the extent you're missing the point... it lets people that might not be able to set it up otherwise have secure messaging across desktop and mobile, and a unified place to have all the features that you mentioned vs getting familiar with nc/scp/ftp, grepping chat logs, etc.
That said, they must have one hell of a demo deck (or secret master plan) to get a $1B+ valuation.
One of the most important for our team is the ability to be signed into multiple organisations/accounts at the same time. Slack handles this perfectly, and HipChat not at all. I don't think I've seen a uservoice request with more votes than HipChat has for this http://help.hipchat.com/forums/138883-suggestions-ideas/sugg...
Easy: our entire agency (70+ people, half designers/developers, half management, client and accounts, etc) is using it, no matter how tech-savvy they are.
I love IRC, and I ran an IRC server for us developers for a good 6 months, but got us to switch over to Slack for the sole reason that accounts management and PMs are happy to use it, and we get transparent searching across every chat :)
In retrospect, though, I might've gone too far the other way -- hipchat is pretty bare bones.
And also people who want it, are able to set it up, but would prefer to pay someone else to do it for them. Lots of useful services simply deliver something that people want, could do themselves, but prefer not to. Like and email providers and restaurants.
The valuation "sounds high", but they've shown that they can deliver a product that many users love and many individuals businesses will pay actual money for. I was shocked when I read the amount, but at least they sell a product!
The company you follow sells common stock to its shareholders.
But that's what VCs do - make a large number of bets that will fail and one that blows it out the park.
Their valuation is a reflection of the growth in Slack's business - meaning they have strong enough growth that they can command that kind of valuation on a huge raise. It is also like a reflection on the limited number of companies that have that kind of growth.
But these kind of valuations also create a high-wire act for the companies in my experience. Growth must be maintained at all costs to justify the valuation. They spend like they're going out of style because of this.
Chrome lets you create apps that open in separate windows.[0] Then it's precisely as bad as any other IM app.
> you need to keep an eye on that tab in case something comes up
If your team members don't @ you when something might be relevant to you, sure. However, if they don't, you can just check every hour or so and get back to them. That's the beauty of Slack - it sits somewhere between IM and email, not everything has to be instant (because everything's saved and you can read it at your pace) but it has the ability to be used as such when enough people are around.
Eleven Giants, the team working on repairing Tiny Speck's previous game, uses Slack like this. Nobody's ever all going to be on at the same time, but everyone can join discussions.
> the 'notifications' don't work all the time (Archlinux + Firefox)
Never had this issue - I'd blame you using a "bleeding edge" distro.
I too generally find Slack to be a more appealing user experience, though along with others I find the advantages over, say, Skype plus email to be fairly nugatory.
Because I work on a bunch of different teams for different organisations, I currently have open Slack, HipChat, Skype, and Apple's Messages, and I have to use Google Hangouts (which periodically completely kills Chrome for me) for a daily standup. I sort of miss those happy days when you could just use Adium for everything.
Other group chats I've used don't do this as well. Skype is particularly awful in this regard.
Hopefully with this new money they can invest a bit more in their Android development efforts.
In the press release, Butterfield says: "As the leader of a brand new product category, we have a huge advantage right now."
Does anyone know what product category he's referring to?
Enterprise collaboration seems like a quite old category to me, but maybe this is where I'm missing the point. Would be interested in hearing where I'm wrong.
Of course, you might agree with the person you're responding to and think the differences are being exaggerated. Personally that has not been my experience.
Think of it less as "fancy IRC" and more of "tool that lets people have fewer face-to-face meetings just to catch up on what everyone is doing".
The notifications are clever enough to not ping me again on the phone if the Mac app is already running.
Integration with other things is dead simple - I had Sensu alerts sent to Slack in a matter of minutes.
I don't know. It's instant messaging, it's not like they've reinventing rocket science from scratch, but it's a good implementation of the concept, multiplatform, well integrated.
If they have something solid, that is, a much better solution for an important problem where their solution will have a significant barrier to entry, maybe Fred Wilson's "large network of engaged userrs" who have a significant switching cost, then okay. Do they?
If it's anywhere bear as transformational for other companies, I can see it continuing to grow for a long time.
I appreciate having a lot of messages come through slack rather than clutter up my inbox.
As far as all the stuff it 'already does', isn't it more convenient than a lot of that. It's like a lightweight and snappier version in my opinion.
-you need to keep an eye on that tab in case something comes up,
-the 'notifications' don't work all the time (Archlinux + Firefox)
It's like somebody took all the bad qualities of IRC, and shoehorned it into a web-page and all the horror that brings. The features that I don't understand:
search-able logging of messages. Email and/or Pidgin already does that.
Group messages: Email already does that.
Transferring of files: Email and/or corporate LAN shares already do that.
But it does add the necessity of stopping my workflow every 5-10 minutes so I can check to see if there are any messages that _might_ apply to me.
The quicker it can be killed with fire the happier I will be. Or am I missing the point? curmudgeonly - check
beard - check
Unix admin - check
Perhaps there is no hope for me. Next thing you know people will want to take pictures with their cellphones! =)