4 ms·
(1) this is awesome (2) http://glassbowl.info/ http://glassbowl.info/ is not leading for me (3) If you did scrape LinkedIn, you probably violated their ToS, s
by calcsam 11y ago
(1) this is awesome
(2) http://glassbowl.info/ http://glassbowl.info/ is not leading for me
(3) If you did scrape LinkedIn, you probably violated their ToS, so you may not want to admit this publicly in case this goes anywhere :)
- garrettheaver 11y agoCame back here to suggest your point 3. I sense a cease and desist is on the way...
- elaineo 11y agoCan I plead ignorance? :X
- garrettheaver 11y agoYou can always try I guess. Whether or not it works is another story :-p I started using tor for this type of thing. It's very handy in that it generates a new circuit every 10 minutes or so and hence you get a new exit node.
- elaineo 11y agoRe #2 - sorry! I had to restart the server. Try again now :)
- personjerry 11y agoFor me, it's now saying: "Oops! LinkedIn error. Please check your url."
- elaineo 11y agoUsually it goes away if you wait a little bit. I think they do some rate-limiting. Also they'll probably block requests from my server soon ;)
- prairiedogg 11y agoCould you get away with allowing folks to manually paste in the HTML of their own linkedin page, or perhaps upload a PDF version of their linked in page? Are you scraping the page for input params? Would it be possible to just expose an API (or web forms that point there) to let folks put in those parameters manually?
- elaineo 11y agooy, that would actually have been a much better way of doing it. I was trying to be clever and keep the UI simple, and totally didn't expect to hit rate limits so quickly.
- wisevehicle 11y agoI want to +1 this idea :)
- elaineo 11y agoOkay, I added a field to manually paste in the HTML! Thanks for the suggestion :)