Slack Taps Goldman Sachs to Lead IPO
reuters.com
reuters.com
[0] https://support.discordapp.com/hc/en-us/articles/36001265609...
Splitting it in two is of course possible, but that comes with its own set of caveats in my opinion. Enterprise users have quite a different set of priorities from gamers...
Either way, I've worked at companies that don't know what they want to be, and it frankly sucks for many reasons. Good for Discord to know what they want to be.
Doesn't seem silly to me if it's working for them.
Despite having this, all the traders just end up using Bloomberg chat. GS tooling often gets in your way more than it helps.
[1] https://techcrunch.com/2017/05/16/symphony-a-messaging-app-b...
[2] https://www.ft.com/content/f16d73ee-a910-11e7-ab55-27219df83...
Since they took capital, the funds associated with their prior fundraising rounds ($1.2B total) likely have 10 year horizons. Investors are looking to recoup their investment during that window. Having the company stay private means that they either need to raise a new round to buy out their old investors, or they need to return sufficient profit over a short window (just a few years) that their investors are happy with the dividend.
Not to mention, there are tons of advantages in having access to the public markets. It's definitely a headache and work, but it's not without its benefits.
My guess is
* liquidity for employees and investors
* access to even greater amounts of capital
* access to capital that might not be as fickle as private investors
How is Webex competing with Slack? Slack is for chat-based collaboration with people in your workplace. Webex is for scheduling video calls.
Is there some overlapping use-case of either one that I'm missing?
That said, I think it's naive and foolish to have an expectation of privacy on your work slack. Should you have privacy? Yes, absolutely. Do I expect it? No, not at all.
I view it much like having a conversation in the hallway or by the watercooler. It would be creepy and weird, and unexpected, to have microphones and cameras all over the office so the boss can record your conversations and eavesdrop whenever they like.
It also screams micro-management if the boss needs to drop in, even if you are just using it "for the purpose of doing [your] job."
I tend to feel that if you trust your employees so little, then you should just fire them. Conversely if my employer trusted me so little, I should probably quit.
Where I would probably make an exception would be if one of the employees filed an HR complaint or something, then I think looking at the existing record would be fine. But, it should be limited in scope to that incident.
Just because using the ability to read private messages screams micro-management, it doesn't mean that it's not occasionally necessary to discover instances of harassment or abuse.
It has already been demonstrated that monitoring employee email to ensure that confidential information is not being shared is not consider proportionate (in a normal workplace), so I don't believe that monitoring direct messages in Slack would be lawful here.
You probably shouldn't expect privacy in any workplace app, or even when connected to a company network, given how many companies route traffic through proxies that inspect packets for data exfiltration and who knows what else.
But I agree, don't expect any privacy on a company network, with a company machine, and/or on company-paid apps.
All that said, it's also not really true that "your boss" can read your private messages, in practice most of the time. Most companies that do this kind of data export just dump it to a warehouse and hold it for safe keeping just in case. Some random director of engineering probably couldn't get access to it unless they were willing to jump through a lot of hoops. Though, Slack's Discovery API does seem to make it easy to create user-friendly interfaces for searching through private messages. But I doubt a lot of companies are doing that.
[1] https://get.slack.help/hc/en-us/articles/204897248-Guide-to-...
Side thought: I wonder if Flickr could have become what Instagram is today if not for the acquisition!
Turns out there's not much of a monetizable market for professional and hobbyist photographers to have a portfolio-like social photo service. Or no one's found it yet.
“When Richardson joined Instagram in February 2012, at age 26, the former art history major was drawn to what was then a fast-growing indie platform for photographers, hipsters and artistic-types who wanted to share interesting or beautiful things they discovered about the world. At that time, Instagram was “a camera that looked out into the world," said one of the company’s first engineers, "versus a camera that was all about myself, my friends, who I’m with.” https://www.washingtonpost.com/amphtml/technology/2018/11/14...
The only reason there was a gap in the iPhone market for Instagram to fill was that internal warring at Yahoo kept them from launching a good iPhone app. If Flickr has just taken their existing smartphone features and put them in an iPhone app on iPhone launch day, they would have been the dominant social photo sharing app on the iPhone, just at they were on the web.
Once everyone in your 1000+ company is using it, its hard to get them all to switch to another chat product. You got saved conversations, workflows, integrations, etc.
It's one of the lowest switching costs. A few weeks lost to redo the integrations that really matter. That's about it.
Zero benefit in the end, they're all a basic chat with some fanciness of top. It's just time wasted for all the users who hates change and have to learn a new tool for no benefit.
Git only impacts developers, a smaller user base, who can figure out how to use a new website.
That being said. They are both easy switch. Just need to update the URL to the new tool.
Teams treats each message as if it is a “post” that is meant to be “commented” on and is extremely oriented around thread-based communication. Each “top-level” message gets borders and huge margins and padding in the UI. As a result, you can see fewer messages on the screen at a time. By contrast, Slack has the feature of threads, but defaults to being focused on the general flow of conversation, with more messages on the screen at a time.
Some people probably like the thread-based communication model Teams uses. I do not count myself among them.
It doesn't seem to do well with images that only exist on the clipboard being pasted over. Which made for a lot of my previous slack use. Now my desktop is littered with image i never cared to save in the first place.
Scrolling message history is a pain. Jittery, seems to be loading a total of like 5 messages at a time so it keeps needing to pause to load.
Sometimes it'll just go all white for a couple seconds
There was something I didn't like about copy pasting text in it that I can't remember right now.
For code that's multiple lines long and where you don't care about syntax highlighting, you can surround the code in triple backticks a la (i.e. type first set of triple backticks, paste in code, type in second set of triple backticks):
```#include <stdio.h>
int main() {
printf("Hello world\n");
}```
For code where you want syntax highlighting, I do think you either need to drag the relevant text file into the Slack window or use the '+' button to the left of the text box.If the former, I'm not sure that's possible given what we know about their cap table. And if the latter, wouldn't fiduciary duty to minority shareholders still require the board to accept a sufficiently good offer?
Or talk?
Or hangouts?
Or plus?
Or... fuck, i honestly don’t know what Google is pushing for chat today.
https://9to5google.com/2018/12/02/google-hangouts-shutting-d...
https://www.blog.google/products/messages/latest-messages-al...
Disclaimer: I work at Google.