You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Note that all the pictures are from LinkedIn profile pictures. [Related to issue #12]
What has been done:
Added some missing LinkedIn profile links and fixed some [people with similar names].
Adjusted some name spelling.
Added TODOs for remaining students.
Peter, Marim, & Mariem all have their profile pictures as viewable by connects only (Probably). We should get their permission to make sure they are okay with the pictures being on the website. [for privacy reasons]
P.S: Ignore the second commit since I already discarded the changes in it and merged the latest commits on the main repo with mine.
All the pictures are from LinkedIn profile pictures.
- Adjusted some name spelling.
- Added TODOs for remaining students.
- Peter, Marim, & Mariem all have their profile pictures as viewable by connects only (Probably). We should get their permission to make sure they are okay with the pictures being on the website. [for privacy reasons]
How could you pull off this magnificence? It had crossed my earlier, but I quickly concluded it would be too hard. You must either be an exceptionally zealous person to pull it off by hand or an exceptional soviet hacker to pull it off with automation. I wonder which? In all cases:
As much as I'd like to flex much my Python scripting and hacking skills, this was all done by hand.
LinkedIn's security is top notch and the existing APIs that perform user search and data scraping either require an applying for a waitlist or having a short free trial that limits search to a 100 profiles/months. Both solutions didn't seem like a good long term solution, so what's left would be writing a script to scrape LinkedIn. Haven't tried the last option yet, but it can be left a future work.
As much as I'd like to flex much my Python scripting and hacking skills, this was all done by hand. LinkedIn's security is top notch and the existing APIs that perform user search and data scraping either require an applying for a waitlist or having a short free trial that limits search to a 100 profiles/months. Both solutions didn't seem like a good long term solution, so what's left would be writing a script to scrape LinkedIn. Haven't tried the last option yet, but it can be left a future work.
Still is significant effort that would not be carried on by any average individual, thank you so much.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note that all the pictures are from LinkedIn profile pictures. [Related to issue #12]
What has been done:
P.S: Ignore the second commit since I already discarded the changes in it and merged the latest commits on the main repo with mine.