Live data from Hacker News

LinkedIn suffers DNS hijack

alpha.app.net

41–50 of 95 posts

Re: LinkedIn suffers DNS hijack

#41
post #28

DNS hacks on big public companies seems like a big security oversite form the linkedin team. wow. Perhaps my HTTPS anywhere extension could have helped folks.

While I love your HTTPS anywhere extension and thought (cough) have it installed, I was dismayed that I was allowed to connect to http://www.linkedin.com/.

Then I found out it wasn't synched over last time I changed laptops.

Installing it now. Thanks for the great work!

Re: LinkedIn suffers DNS hijack

#42
I'm done with LinkedIn.

I've been on the fence about it for a year now. I get more recruiter spam than value.

I'm also a bit too old for the schadenfreude that accompanies news of my overpaid friends getting canned. I'm running my own race these days and I've never been happier since I stopped comparing my lot in life to the few lucky SOBs I know that survived the cull of sub-prime.

I think a better strategy is (1) your own domain and/or (2) a site on github with actual code to validate* your talents.

*I hate those "Joe Schmo supported you skill in [insert banal technical skill here]" messages. I once put down C++ because I had been working with it for a couple years. Then, I thought better (I would not take a C++ programming job. Period. Hate that language.) and took it off. Next thing I know, I've got coworkers supporting my C++ acumen and LinkedIn trying to push it back on my profile. Ugh. I call that invasive feature creep.

On top of that, they seem to leave the backdoor open a bit too much for a company with $20b market cap.

Re: LinkedIn suffers DNS hijack

#43
post #40
post #31

Earlier quoted context omitted.

I often describe LinkedIn as a bunch of business people, who have a website. It's not a tech company and the hiring reflects that.

dsl, no offense, but you seem to have a problem with any company that doesn't hire/provide employment to your average local community college CS grad and instead hires globally based purely on merit. Linkedin interviews are on par with facebook/google et al.

Really, now the sock puppets are coming out?

I hire people purely on technical merit, I don't even bother reviewing educational credentials. I am opposed to abusing the H1-B system rather than opening offices overseas to bring in skilled labor and raise local standards of living.

Re: LinkedIn suffers DNS hijack

#46
post #42

I'm done with LinkedIn. I've been on the fence about it for a year now. I get more recruiter spam than value. I'm also a bit too old for the schadenfreude that accompanies news of my overpaid friends getting canned. I'm running my own race these days and I've never been happier since I stopped comparing my lot in life to the few lucky SOBs I know that survived the cull of sub-prime. I think a better strategy is (1) y…

>I think a better strategy is (1) your own domain and/or (2) a site on github with actual code to validate* your talents.

That's because their target audience is not restricted to the tech savvy. Not everyone knows how to host and maintain their own domain. Not everyone uses github or know what git is.

This was basically why LinkedIn came into fruition in the first place.

Re: LinkedIn suffers DNS hijack

#47
post #43
post #40

Earlier quoted context omitted.

dsl, no offense, but you seem to have a problem with any company that doesn't hire/provide employment to your average local community college CS grad and instead hires globally based purely on merit. Linkedin interviews are on par with facebook/google et al.

Really, now the sock puppets are coming out? I hire people purely on technical merit, I don't even bother reviewing educational credentials. I am opposed to abusing the H1-B system rather than opening offices overseas to bring in skilled labor and raise local standards of living.

Opening new offices overseas is obviously not feasible in all cases and scalable.

And I don't think companies like Linkedin, Facebook, Google etc abuse the H1-B system. People there are genuinely smart.

However, there are certain consulting companies like Accenture, Infosys, TCS, Cognizant, various body shops etc that abuse the shit out of it. The govt. should definitely be more proactive in banning these companies and not play to the likes of NASSCOM. Infact, I'd argue that the govt. should come up with a whitelist of companies to grant H1-Bs to.

Re: LinkedIn suffers DNS hijack

#48
post #42

I'm done with LinkedIn. I've been on the fence about it for a year now. I get more recruiter spam than value. I'm also a bit too old for the schadenfreude that accompanies news of my overpaid friends getting canned. I'm running my own race these days and I've never been happier since I stopped comparing my lot in life to the few lucky SOBs I know that survived the cull of sub-prime. I think a better strategy is (1) y…

>I think a better strategy is (1) your own domain and/or (2) a site on github with actual code to validate* your talents. That's because their target audience is not restricted to the tech savvy. Not everyone knows how to host and maintain their own domain. Not everyone uses github or know what git is. This was basically why LinkedIn came into fruition in the first place.

I totally get it. I'm only talking about me.

I'm sure this community is generally capable of rolling their own LinkedIn.

Post reply on HN