Bare (no rDNS) IP belongs to the LinkedIn corporate mothership:
216.52.242.14 [projecthoneypot.org...] LinkedInBot/1.0 (compatible; Mozilla/5.0; Jakarta Commons-HttpClient/3.1 +http://www.linkedin.com)
robots.txt? NO
Again part of a Twitter storm but unlike prior visit(s) when it was Host-named. [webmasterworld.com...] Still no direct linked-in connection on/to the site hit.
keyplyr
10:24 pm on Oct 31, 2011 (gmt 0)
Just a FYI - blocking this bot has had no affect on links posted in LinkedIn account nor the timeline.
dstiles
10:54 pm on Oct 31, 2011 (gmt 0)
I allow LinkedIn bots because some of my clients use the service. Not always a welcome service, though: sometimes get mail spam from them.
Staffa
12:11 am on Nov 1, 2011 (gmt 0)
I have not seen it yet but should it come, I have "Jakarta Commons" blocked for years.
Pfui
12:45 am on Nov 1, 2011 (gmt 0)
Speaking of... Spam from LinkedIn users "to become part of his or her professional network" comes in annoying triplets:
Day 00: Invitation to connect on LinkedIn Day 07: Reminder about your invitation from [so-and-so] Day 14: Reminder about your invitation from [so-and-so]
I've never once recognized a sender's name.
Too bad blocking the bot doesn't also stop the spam.
keyplyr
12:55 am on Nov 1, 2011 (gmt 0)
I allow LinkedIn bots because some of my clients use the service. Not always a welcome service, though: sometimes get mail spam from them.
I see absolutely no reason LinkedIn needs to crawl your site because you have a profile there. They are harvesting data for other purposes IMO.
dstiles
10:42 pm on Nov 1, 2011 (gmt 0)
One of the injurious features of linkedin spam is: some of it comes from an ex-client who ran away without paying the bill. I tried telling him the next time he sent me spam I would report him to linkedin but I've never had the time/patience. :(
