Forum Moderators: open
2.) I've had hits from neighboring 69.63.182.122 related to Facebook and using atypical (one new, ugly) UAs. More details here:
php-openid/2.1.1 (php/hphp) curl/7.19.4 : Something new from Facebook comes... [webmasterworld.com]
3.) Historically, my hits from Facebook Hosts/IPs have been link-checking. In the aftermath of the above-mentioned unknowns, I've 403'd all hits. Doing so has had no apparent effect on Facebookers continuing to include (or follow) links.
The only real mentions of this I found on the web were from the honeypot project: [projecthoneypot.org...]
out.250.01.snc1.facebook.com
facebookexternalhit/1.0 (+http://www.facebook.com/externalhit_uatext.php)
21:56:09
out003.05.snc1.tfbnw.net
Facebook share follower
21:57:00
21:57:00
out002.05.snc1.tfbnw.net
Facebook share follower
21:57:00
21:57:00
out001.05.snc1.tfbnw.net
Facebook share follower
21:57:00
21:57:00
21:57:00
Oh, and not a robots.txt URI in the bunch.
Regardless, the first 403 would've been a sufficient signal to better-behaved/programmed apps. Of course, it's up to you what you want to do when they hit you.
When I send a friend a link on Facebook, they (Facebook) take a snapshot of the page I'm sending and post it in the bottom of my message.
However, if they're hitting robots.txt... makes it all the more odd for it's behavior. Why would a screenshot link attachment be reading robots.txt?
Image requests from remote referrers are swapped to a small size .png displaying rhetoric about ethical behavior regarding bandwidth theft, however serving that file 5k Xs an hour to a mass of cost-indifferent teenage girls is not what I had in mind.
Related thread: [webmasterworld.com...]
@dstiles: Certain WHOIS sites showing obtained-without-permission thumbs feature my 403 all too prominently. Nifty thing is, because my 403 displays the visitor's UA and IP, larger shots show bots' IPs and UAs, too. :)