search

initstring / linkedin2username

OSINT Tool: Generate username lists for companies on LinkedIn
MIT License
1.25k stars 185 forks source link

[REQUEST] Add occupation to the list #51

Closed Awaces closed 1 year ago

Awaces commented 1 year ago

Hello

I love this tool, but I feel like I am missing crucial additional information about the scraped targets.... Their occupation in the company. Can you add this function to the script. I'm a noob in python so I won't be able to do it myself.

Edit: the time a person has already been employed is also of interest

Thanks in advance.

initstring commented 1 year ago

Hi @Awaces

Thanks for opening an issue. This was previously discussed here.

I think it might make sense to add it to the raw names file only, so as not to complicate the username lists. I want to be careful not to expand this tool out too much further - it is meant to be a very simple username generation tool, not a full LI scraping tool. The more complex the tool gets, the harder it is to maintain as I have to play cat/mouse anytime LinkedIn makes changes to their site.

Can you describe your use case for requiring occupation names? How would you process and parse the file with names and occupations?

Thanks!

Awaces commented 1 year ago

Hi @Awaces

Thanks for opening an issue. This was previously discussed here.

I think it might make sense to add it to the raw names file only, so as not to complicate the username lists. I want to be careful not to expand this tool out too much further - it is meant to be a very simple username generation tool, not a full LI scraping tool. The more complex the tool gets, the harder it is to maintain as I have to play cat/mouse anytime LinkedIn makes changes to their site.

Can you describe your use case for requiring occupation names? How would you process and parse the file with names and occupations?

Thanks!

Hello @initstring,

Having the raw names list is perfect! I use this tool mainly as a tool for ethical hacking, creating phishing target lists for customers. It can be a hassle to manually identify which individuals to avoid, such as those in IT, management, or HR. If the occupation were included in the raw list, it would make it much easier for me to filter and for the customer to see which department is of the greatest concern.

So it would be very useful if you could add this

initstring commented 1 year ago

Thanks @Awaces, this sounds pretty reasonable.

I've added a working PoC in this branch and will eventually merge it with this PR.

It needs more testing, but let me know what you think.

Awaces commented 1 year ago

Thanks for the quick add!

At first it does perfectly what it has to do!

initstring commented 1 year ago

Thanks for the suggestion, this is done.