search

ptwobrussell / Mining-the-Social-Web-2nd-Edition

The official online compendium for Mining the Social Web, 2nd Edition (O'Reilly, 2013)
http://bit.ly/135dHfs
Other
2.9k stars 1.49k forks source link

How Do I get LinkedIn USER_TOKEN and USER_SECRET #274

Open dbl001 opened 9 years ago

dbl001 commented 9 years ago

USER_TOKEN = '' USER_SECRET = ''

These fields are not displayed in my LinkedIn Developer screen.

I only see:

Authentication Keys

Client ID:
    xxx
Client Secret:
    yyy
ptwobrussell commented 9 years ago

Try the two fields you mention. It may be the case that the user interface has just changed but the underlying intention is the same

---Sent from Boxer | http://getboxer.com

On May 21, 2015 at 1:38:45 PM CDT, dbl001 notifications@github.com wrote:USER_TOKEN = '' USER_SECRET = '' These fields are not displayed in my LinkedIn Developer screen. I only see: Authentication Keys Client ID: xxx Client Secret: yyy —Reply to this email directly or view it on GitHub.

dbl001 commented 9 years ago

auth = linkedin.LinkedInDeveloperAuthentication(CONSUMER_KEY, CONSUMER_SECRET, USER_TOKEN, USER_SECRET, RETURN_URL, permissions=linkedin.PERMISSIONS.enums.values())

So try using: CONSUMER_KEY, CONSUMER_SECRET (which is available from LinkedIn) in the USER_TOKEN, USER_SECRET fields of the linkedin.LinkedInDeveloperAuthentication method?

dbl001 commented 9 years ago

It didn't work. Any other ideas?

dbl001 commented 9 years ago

I got this document from LinkedIn:

https://developer.linkedin.com/blog/posts/2015/transition-faq

Does it mean your LinkedIn code will no longer work?

bashyroger commented 9 years ago

Yes, The Linkedin Api is (in my opinion) basically closed now, except when: 1) You are a partner / bring a lot of money 2) You use the api to complement your company's career pages, though you first have to apply for that....

dbl001 commented 9 years ago

Do you think I’m allowed to screen scrape the data?

On Jun 1, 2015, at 5:52 AM, Rogier Werschkull notifications@github.com wrote:

Yes, The Linkedin Api is (in my opinion) basically closed now, except when: 1) You are a partner / bring a lot of money 2) You use the api to complement your company's career pages, though you first have to apply for that....

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-107414535.

bashyroger commented 9 years ago

Officially, no: https://help.linkedin.com/app/answers/detail/a_id/56347/~/linkedins-scraping-software-policy Technically, it is possible, for instance using http://scrapy.org/ If you do this you have to be very careful not to issue too many request, otherwise you will be blocked for a certain amount of time. And you even risk having your account shut down if you are identifiable...

dbl001 commented 9 years ago

Is this the correct iPython notebook interface? I can’t seem to find the notebooks. I’m running the notebook server natively on my Mac with an Anaconda stack. conda update ipython ipython-notebook ipython-qtconsole

On Jun 1, 2015, at 6:17 AM, Rogier Werschkull notifications@github.com wrote:

Officially, no: https://help.linkedin.com/app/answers/detail/a_id/56347/~/linkedins-scraping-software-policy https://help.linkedin.com/app/answers/detail/a_id/56347/%7E/linkedins-scraping-software-policy Technically, it is possible, for instance using http://scrapy.org/ http://scrapy.org/ If you do this you have to be very careful not to issue too many request, otherwise you will be blocked for a certain amount of time. And you even risk having your account shut down if you are identifiable...

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-107420280.

dbl001 commented 9 years ago

Never mind! I started $ ipython notebook in the wrong directory.

On Jun 1, 2015, at 8:35 AM, David Laxer davidl@softintel.com wrote:

Is this the correct iPython notebook interface? I can’t seem to find the notebooks. I’m running the notebook server natively on my Mac with an Anaconda stack. conda update ipython ipython-notebook ipython-qtconsole <Screen Shot 2015-06-01 at 8.34.53 AM.png>

On Jun 1, 2015, at 6:17 AM, Rogier Werschkull <notifications@github.com mailto:notifications@github.com> wrote:

Officially, no: https://help.linkedin.com/app/answers/detail/a_id/56347/~/linkedins-scraping-software-policy https://help.linkedin.com/app/answers/detail/a_id/56347/%7E/linkedins-scraping-software-policy Technically, it is possible, for instance using http://scrapy.org/ http://scrapy.org/ If you do this you have to be very careful not to issue too many request, otherwise you will be blocked for a certain amount of time. And you even risk having your account shut down if you are identifiable...

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-107420280.

dbl001 commented 9 years ago

Is this LinkedIn people-search API Query also closed?

u = "https://api.linkedin.com/v1/people-search/%s:(relation-to-viewer:(related-connections))?format=json" % result["id"]

On Jun 1, 2015, at 4:52 AM, Rogier Werschkull notifications@github.com wrote:

Yes, The Linkedin Api is (in my opinion) basically closed now, except when: 1) You are a partner / bring a lot of money 2) You use the api to complement your company's career pages, though you first have to apply for that....

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-107414535.

ptwobrussell commented 9 years ago

As I understand it, the LinkedIn API is effectively closed for data mining as outlined in Chapter 3 of MTSW2E. Most of the examples still work, however, given that they leverage the CSV download of your contacts. As someone else has pointed out, you can page scrape, but that's violating the ToS, so do it at your own peril ;)

On Wed, Jul 29, 2015 at 11:57 AM, dbl001 notifications@github.com wrote:

Is this LinkedIn people-search API Query also closed?

u = " https://api.linkedin.com/v1/people-search/%s:(relation-to-viewer:(related-connections))?format=json" % result["id"]

On Jun 1, 2015, at 4:52 AM, Rogier Werschkull notifications@github.com wrote:

Yes, The Linkedin Api is (in my opinion) basically closed now, except when: 1) You are a partner / bring a lot of money 2) You use the api to complement your company's career pages, though you first have to apply for that....

— Reply to this email directly or view it on GitHub < https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-107414535 .

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-126016851 .

dbl001 commented 9 years ago

Thanks.

I got the CSV downloads yesterday.

David-Laxers-MacBook-Pro:testing davidlaxer$ ls -l ~/Downloads/LinkedInDataExport_07-28-2015/ total 3296 -rwxr-xr-x@ 1 davidlaxer staff 13673 Jul 28 14:35 -1169023372.jpg -rwxr-xr-x@ 1 davidlaxer staff 3447 Jul 28 14:35 1381476224.jpg -rwxr-xr-x@ 1 davidlaxer staff 359 Jul 28 14:35 1495406907.jpg -rwxr-xr-x@ 1 davidlaxer staff 823 Jul 28 14:35 1886570078.jpg -rwxr-xr-x@ 1 davidlaxer staff 122 Jul 28 14:35 Account Status History.csv -rwxr-xr-x@ 1 davidlaxer staff 4604 Jul 28 14:35 Ad Targeting.csv -rwxr-xr-x@ 1 davidlaxer staff 2776 Jul 28 14:35 Ads Clicked.csv -rwxr-xr-x@ 1 davidlaxer staff 144 Jul 28 14:35 Certifications.csv -rwxr-xr-x@ 1 davidlaxer staff 2334 Jul 28 14:35 Comments.csv -rwxr-xr-x@ 1 davidlaxer staff 183960 Jul 28 14:35 Connections.csv -rwxr-xr-x@ 1 davidlaxer staff 388 Jul 28 14:35 Courses.csv -rwxr-xr-x@ 1 davidlaxer staff 627 Jul 28 14:35 Education.csv -rwxr-xr-x@ 1 davidlaxer staff 406 Jul 28 14:35 Email Addresses.csv -rwxr-xr-x@ 1 davidlaxer staff 46592 Jul 28 14:35 Endorsement Received Info.csv -rwxr-xr-x@ 1 davidlaxer staff 22800 Jul 28 14:35 Likes.csv -rwxr-xr-x@ 1 davidlaxer staff 25154 Jul 28 14:35 Login Attempts.csv -rwxr-xr-x@ 1 davidlaxer staff 556 Jul 28 14:35 Mobile Applications.csv -rwxr-xr-x@ 1 davidlaxer staff 3674 Jul 28 14:35 Positions.csv -rwxr-xr-x@ 1 davidlaxer staff 812 Jul 28 14:35 Profile.csv -rwxr-xr-x@ 1 davidlaxer staff 7264 Jul 28 14:35 README.txt -rwxr-xr-x@ 1 davidlaxer staff 6016 Jul 28 14:35 Recommendations Received.csv -rwxr-xr-x@ 1 davidlaxer staff 326 Jul 28 14:35 Registration Info.csv -rwxr-xr-x@ 1 davidlaxer staff 623804 Jul 28 14:35 Search Queries.csv -rwxr-xr-x@ 1 davidlaxer staff 446 Jul 28 14:35 Security Challenges.csv -rwxr-xr-x@ 1 davidlaxer staff 666770 Jul 28 14:35 Shares.csv -rwxr-xr-x@ 1 davidlaxer staff 1234 Jul 28 14:35 Skills.csv David-Laxers-MacBook-Pro:testing davidlaxer$

Do you know if it includes: (relation-to-viewer:(related-connections))?

also, Is there an update to MTSW2E? O’Reilly shows the last revision was July 10, 2014.

On Jul 29, 2015, at 10:09 AM, Matthew A. Russell notifications@github.com wrote:

As I understand it, the LinkedIn API is effectively closed for data mining as outlined in Chapter 3 of MTSW2E. Most of the examples still work, however, given that they leverage the CSV download of your contacts. As someone else has pointed out, you can page scrape, but that's violating the ToS, so do it at your own peril ;)

On Wed, Jul 29, 2015 at 11:57 AM, dbl001 notifications@github.com wrote:

Is this LinkedIn people-search API Query also closed?

u = " https://api.linkedin.com/v1/people-search/%s:(relation-to-viewer:(related-connections))?format=json" % result["id"]

On Jun 1, 2015, at 4:52 AM, Rogier Werschkull notifications@github.com wrote:

Yes, The Linkedin Api is (in my opinion) basically closed now, except when: 1) You are a partner / bring a lot of money 2) You use the api to complement your company's career pages, though you first have to apply for that....

— Reply to this email directly or view it on GitHub < https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-107414535 .

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-126016851 .

— Reply to this email directly or view it on GitHub https://github.com/ptwobrussell/Mining-the-Social-Web-2nd-Edition/issues/274#issuecomment-126020878.