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

Integrating Microsoft and LinkedIn

linkedin.com

Post reply on HN
Print view View original

41–50 of 75 posts

Re: Integrating Microsoft and LinkedIn

#41

Post by mindcrime »

arebop wrote: post #16
mindcrime wrote: post #13

I can't help but suspect this will be the end of LinkedIn. Why would any firm want Microsoft to have control of so much potential competitive intelligence? As well as the ability to potentially interrupt / snoop on critical communications? Yeah, LI messages aren't as important to most people as plain email, but LI messages are used for a lot of recruiting and B2B sales stuff. Think about it like this: if I compete wi…

It's not really up to other firms though, it's up to the employees who see value in the social network.

Strictly speaking that's true. But employers have a fair amount of leverage, especially in terms of recruiting and what-not. I suspect a lot of people are on LI because it serves as a sort of default online resume, and if companies quit recruiting through LinkedIn and switch to something else, I think the users might follow.

OTOH, maybe most people only use LI as an online Rolodex and maybe it'll all turn out to be a moot point. But it still seems dodgy to me to have a major industry player like MS owning LinkedIn. I think I'd find it questionable if anybody else had acquired them as well, although Microsoft's history does add some emphasis to the whole thing in my view.

Re: Integrating Microsoft and LinkedIn

#42

Post by bad_user »

mindcrime wrote: post #36
bad_user wrote: post #19

Earlier quoted context omitted.

You're exaggerating. Microsoft and Google literally own your email, while only recruiters check their LinkedIn messages, most of them being spam.

while only recruiters check their LinkedIn messages, most of them being spam That does not jibe with my experience at all. And it goes beyond the messaging thing anyway. LI hosts job postings directly, and has a lot of internal information about all sorts of companies. Now you might say "well, somebody could mine that stuff anyway", and that might be true. But the LI API has some limits and scraping is a PITA.. but n…

> "The two biggest tactical mistakes you can make are staging a ground invasion of Russia in the winter, and partnering with Microsoft"

While I hole heartily agree with that line of reasoning, in this instance they are buying LinkedIn, not partnering with them. Skype is still alive.

My problem is that LinkedIn is an overvalued property. I mean OK, Microsoft and others could extract useful data from it, but it's nothing you can't infer from other places IMO.

And mark my words, but Facebook will eat their lunch. Maybe that's why Microsoft bought LinkedIn, as a defensive move. Time will tell.

Re: Integrating Microsoft and LinkedIn

#43

Post by thebigshane »

bjornlouser wrote: post #38
ryandrake wrote: post #34

Earlier quoted context omitted.

Just a pet peeve, but please re-consider the casual use of the word "poach" when referring to companies hiring employees. It reduces a worker's agency to that of a farm animal or wild game, as if they were owned by their employer and "stolen" away by some other employer. I think we can all agree that we are not the property of our employers, so the word "poach" is pretty inappropriate and I'd argue moderately offensi…

Use "lure" ... no, that implies that employees are like rodents. Next time try "propositioned"... no that's for whores. This is tough stuff.

"recruit"

It isn't that hard :)

Re: Integrating Microsoft and LinkedIn

#44

Post by mindcrime »

bad_user wrote: post #42
mindcrime wrote: post #36

Earlier quoted context omitted.

while only recruiters check their LinkedIn messages, most of them being spam That does not jibe with my experience at all. And it goes beyond the messaging thing anyway. LI hosts job postings directly, and has a lot of internal information about all sorts of companies. Now you might say "well, somebody could mine that stuff anyway", and that might be true. But the LI API has some limits and scraping is a PITA.. but n…

> "The two biggest tactical mistakes you can make are staging a ground invasion of Russia in the winter, and partnering with Microsoft" While I hole heartily agree with that line of reasoning, in this instance they are buying LinkedIn, not partnering with them. Skype is still alive. My problem is that LinkedIn is an overvalued property. I mean OK, Microsoft and others could extract useful data from it, but it's nothi…

While I hole heartily agree with that line of reasoning, in this instance they are buying LinkedIn, not partnering with them.

Right, the point referring to that old saw was more of a comment on Microsoft's trustworthiness in general. That is, it is a suggestion that Microsoft are not to be trusted in terms of what they might do with the LI data.

I mean OK, Microsoft and others could extract useful data from it, but it's nothing you can't infer from other places IMO

Yeah, that's true.

Re: Integrating Microsoft and LinkedIn

#46

Post by mpweiher »

bad_user wrote: post #19
mindcrime wrote: post #13

I can't help but suspect this will be the end of LinkedIn. Why would any firm want Microsoft to have control of so much potential competitive intelligence? As well as the ability to potentially interrupt / snoop on critical communications? Yeah, LI messages aren't as important to most people as plain email, but LI messages are used for a lot of recruiting and B2B sales stuff. Think about it like this: if I compete wi…

You're exaggerating. Microsoft and Google literally own your email, while only recruiters check their LinkedIn messages, most of them being spam.

My primary e-mail is hosted by a small private provider. My secondary e-mail is hosted by a different small private provider. Then come Apple, Google (mostly for groups) and Microsoft.

Re: Integrating Microsoft and LinkedIn

#47

Post by jorts »

mpweiher wrote: post #46
bad_user wrote: post #19

Earlier quoted context omitted.

You're exaggerating. Microsoft and Google literally own your email, while only recruiters check their LinkedIn messages, most of them being spam.

My primary e-mail is hosted by a small private provider. My secondary e-mail is hosted by a different small private provider. Then come Apple, Google (mostly for groups) and Microsoft.

It's probably safe to assume that a good number of the people that you email use email hosted by Google, Microsoft, etc..., which exposes many of your emails to them.

Re: Integrating Microsoft and LinkedIn

#48

Post by binthere »

gk1 wrote: post #30

> Redefining social selling through the combination of Sales Navigator and Dynamics 365 When the acquisition was first announced, I stated that Salesforce should be very concerned.[0] Account-based marketing (what they're calling "social selling") is how successful startups (and others) sell to enterprises these days, and they're willing to shell out cash to software that helps them do that.[1] Having consulted many…

Your comment is the only intelligent comment on this thread.

Re: Integrating Microsoft and LinkedIn

#49

Post by bostik »

JamilD wrote: post #35

• LinkedIn notifications within the Windows action center • Enabling members drafting résumés in Word to update their profiles, and discover and apply to jobs on LinkedIn • Extending the reach of Sponsored Content across Microsoft properties I can't help but feel that the direction they're taking this in will be horrible for the Microsoft experience. It looks like they're trying to monetize LinkedIn integration in Wi…

Hi, I see you're updating your CV.

Would you like me to share it with every recruiter in your extended network? How much are you willing to pay that I don't share it with your coworkers?

Love, Linky.

Re: Integrating Microsoft and LinkedIn

#50

Post by Annatar »

I remember back in the day, 1997, when Hotmail ran on FreeBSD and was actually a decent free web mail service.

Then Microsoft bought them, and the usability has been steadily going down since, until I eventually was forced to abandon it: it couldn't even handle plain text ASCII e-mail properly any more (\n's would be eaten and sent e-mail would end up being one huge line).

But of course, it will be all different with LinkedIn this time. Of course it will.

Post reply on HN