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.
It is a self-updating rolodex, Outlook Contacts list, phone book, whateveryouwanttocallit.
I really don't want to bookmark 300+ individual pages that all have different creative layouts, get moved, etc. My LinkedIn profile stays up-to-date, you update yours, that's the implicit deal. And we all profit from it. all being defined as a western work related group, english spoken. this is not facebook. Link your gitbub repo from there, absolutely, good idea, but having LinkedIn as your standardized contact info is very valuable.
is LinkedIn managed in a bad way? sure. But for some reason the modern business world has chosen it to focus on it. Xing and other local players never grew enough. the benefits of starting out it in the US. all the surrounding crap they're building is fluff, their core feature is being a global rolodex. would love to slap sense into their product management team.
As of this writing, I only have my undergrad and grad school names listed. I don't think I even have my areas of study on there.
Works perfectly as a rolodex.
Which is why I completely disabled it. Having the ability to see who viewed your profile seemed cool at first, but then again, it's useless and the downsides are great.
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'm sure this community is generally capable of rolling their own LinkedIn.
¹ yes, I also hate that word, but there you go.
Possibly, but that's for programmers. There are more professions out there.
I just closed my account too. The help page said that my account would no longer be visible on LinkedIn, but after closing and logging out, I still get the "sign up to see the full profile" bait on visiting my old URL (search result from Google).
I would have thought with Java, C#, objective C, php, node, etc that I'd be a good catch but apparently not!
It does sound like LinkedIn's NOC are playing the blame game already. Well, I guess they've gotta get all those spamming recruiters & sales reps back online.
EDIT: heh, maybe it was The New Guy:
edit: and I mean the exact same issue, it was resolving to a confluence owned IP that was serving a squatter page for the domain.
considering a lot of their subdomains are still hijacked at this point those cookies are being sent to them
Linkedin interviews are on par with facebook/google et al.
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.
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.
One of the DNS issues I tried to fix with NIS+ was the 'maintaining a list of trusted servers' problem by distributing the management of the authoritative servers. Trust was built bottom up, and authority came top down.
The way it worked was that clients used a 'coldstart' file which was the (small number) of servers you trusted to provide your namespace lookups. You to their public key and you put it into your coldstart file. Similarly, a server put the key(s) of the servers it trusted above it in the name space in its coldstart file. And at company 'root' level was a set of servers run by a trusted authority.
Locating the authoritative name server for x.y.z from p.q.z (same as DNS root is rightmost) client in x.y.z asks its server for a trusted y.z server, gets it, and asks that server for a trusted z. server, then asks that server for a q.z. server and finally for a p.q.z. server. Once this has happened once you know trusted servers can can jump to the nearest one to start resolving a new path in the namespace.
It was slower on initial lookup and then just as fast as DNS on later ones.
It had the downside that compromised (or borked) high level servers could send you on a different path to different root if the server above them was incorrect.
It is one of the more fun problems in the whole name/directory service space.
Do you know of any designs that require a quorum at each level prior to trust? BitCoin seems to be having success with this model, but I'm wondering if anyone's built something like that with the primary intent of creating a directory service.
That said, your idea about poaching the Bitcoin quorum ideas is a good one. Essentially a data structure, equivalent to the block chain, where it only gets authenticated if enough people ack that its the most valid version of reality. Probably a publishable paper in exploring that question.
You may see an email from me in the next few weeks asking for feedback on such a paper.
I can't tell if this is sarcasm or a serious comment. Could you elaborate on this comment? I don't get why a link by app.net would be news worthy.
Looks like the app.net post was by a founder so I would take that with a grain of salt.
Edit: While I'm at it according to https://twitter.com/mikegreenspan , the submitter also works at app.net.
Important Notice [20th June, 2013]
Confluence Networks is a Colocation & Network service provider having tie-ups with data centers across various geographical regions. We don't host any services ourselves. Starting few hours ago, we received reports about some sites (including linkedin.com) pointing to IPs allotted to our ranges. We are in touch with the affected parties & our customer to identify the root cause of this event.
Note that it has already been verified that this issue was caused due to a human error and there was NO security related issue caused by the same. More details will be provided shortly.
I'm trying to find other subdomains that might be still pointing there.
edit: i'm enumerating all the linkedin.com hosts using a dict. 80% of A records are returning the rogue IP 204.11
edit: 96 records still pointing at the rogue server, here is a dump I just uploaded:
short TTL's on a lot of these domains
I just ran it again this time using Google name servers and still a lot of subdomains are pointing to the 214 server. confirmed it running against their NS, which means it hasn't been changed yet.
The 214.-.-.- is some British Virgin Islands allocation?
OrgName: Confluence Networks Inc
Address: 3rd Floor, Omar Hodge Building, Wickhams
Address: Cay I, P.O. Box 362
City: Road Town
[prhodes@captainchaos ~]$ whois email@example.com
# available at: https://www.arin.net/whois_tou.html
# Query terms are ambiguous. The query is assumed to be:
# "n 184.108.40.206"
# Use "?" to get help.
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=220.127.116.11? showDetails=true&showARIN=false&ext=netref2
LinkedIn Corporation INAP-LAX-LINKEDIN-38682 (NET-216-52- 242-0-1) 18.104.22.168 - 22.214.171.124
Internap Network Services Corporation PNAP-8-98 (NET-216-52-0-0-1) 126.96.36.199 - 188.8.131.52
Does that mean I'm still pointing to the legitimate server?
Your secret key shouldn't be compromised, because you're supposed to keep that secret. Also if you use HTTPS for requests you'd still get a cert error even if DNS was routing incorrectly. You're probably fine.
I had a domain (nitren.com), that I let expire after 3yrs and confluence-networks.com back ordered it, I remember looking it up a while back, but if I remember right, all the ip and domains were registered or associated with netsol.
What do you think the main benefits would be?
Perhaps my HTTPS anywhere extension could have helped folks.
Then I found out it wasn't synched over last time I changed laptops.
Installing it now. Thanks for the great work!
It seems this website chooses a random selection from a larger pool of nameservers, so if you refresh the page you may get different results.