91–100 of 145 posts
This is going to destroy Slack
Additionally, Slack now has just about the best tagline in the world: 'We're not Facebook'.
Earlier quoted context omitted.
And Wave was a rehash of Ray Ozzie's Groove, which got bought by Microsoft when they hired him, and then they shelved it. This was c. '97, so how much more was Ozzie ahead of his time, and when is it going to be BE time for this? I still want it. I think the problem with Groove was that it stored data on your local machine, and replicated between clients, and the big companies aren't interested. Best I can figure is…
Microsoft bought Groove in 2005 and renamed the client to Sharepoint Workspace 2010. It was not that great and it got canned. http://de.wikipedia.org/wiki/Microsoft_Groove
So sick of their awful practices.
Not sure why one would need a work specific social network. Work != social, at least for me. I've never shared anything or wanted to on my fb with my work colleagues.
Earlier quoted context omitted.
Maybe that's the point. They noticed declining traffic during work hours and try to reestablish their access to bored employees at work by essentially forcing IT admins to unblock the facebook domain.
I think they might want to sell access to users' private account data to their employers. This will give them an in. They can pretend to sell collaboration tools while they sneak analytics with interesting stuff on the users' personal facebook usage (and maybe browsing habits) in along with it. This won't come immediately, of course.
Why do you think that? User data is the crown jewel and competitive advantage Facebook has over other companies. It would never give up that advantage. This meme refuses to die somehow.
Awesome, pretty soon companies wont have to store any of "their" data on their own servers. Facebook - Company info/announcements/chat OneDrive/Google/Dropbox - Company documents VOIP Services - Company communications All stored in clear-text obviously (or at least not encrypted by company using the service before transfer to said services, same thing really). I myself think this trend is hilariously ridiculous, but…
It is just so expensive to provide 99% uptime on your own servers. Who is going to go into the office at 2:00AM when an executive can't access his power point presentation?
What else could it be used for? Publishing news?
Has anyone seen a work social network that wasn't a joke? We have one, and the only use is that your director/VP asks their org to follow them, and then posts various strategic stuff they want you to see. There's zero peer-to-peer usage at all.
Most communication happens in Outlook/Exchange mailing lists.
I do think that Yammer and it's ilk offer somethings that plain email don't - better attachment integration and history (with email you can't see discussions that occurred before you joined).
One thing I don't like about Yammer (and other social networks for work) is that discussions are very "flat". Contrasted to email discussions at my work, which can get very lengthy and include many branches. They wouldn't scale to Yammer at all.
I couldn't work out from the article if you could run Facebook on your own servers or not. This will be a massive hurdle to jump if they really want to sell to enterprise.
I see them targeting the market of businesses too small to run their own communication infrastructure. The people using google docs and hangouts because it's already there. Or Office 365 because they can't/don't want to host internally. Why would anyone already running their own communication want internal Facebook? Because email lists aren't hip enough?
Let's say you are going to do some work with Molly from the Customer Support department. You don't really know much about her, so you bring her up on the company Facebook, and you find out that you both went to the same university around the same time. You also find out that she has experience in testing. You also see a picture of her, so that you don't have to go walking around customer service area of the office asking if anyone knows where Molly is until she finally overhears you and introduces herself.
Is any of this stuff hard to set up internally? Not really, but someone has to prioritize it, sort through existing options and pick one, or develop it in house, there needs to be support, and maintenance. All barriers to implementing something that can help foster a more open and collaborative culture.