Eric Fourrier

any update on this ?

Hello @rncrtr . I totally agree with the name of this pull request 😄 . We are working on a full markdown on good practices to avoid API keys leaks....

Thanks for reporting the issue and sorry for the false positive :) . It can return a 403 if the link was already clicked. Status code will change really soon...

Thanks for your feedback :). we will definitely look into it for the link for the false positive button. For the secret detection part we are working on excluding Google...

Should be fixed right now thanks, closing the issue

hi @rt0161 look at this [issue](https://github.com/ericfourrier/scrape-linkedin/issues/8)

Linkedin blacklist ip's from cloud providers and if you are making too many requests with your personal ip you will get this error. to be sure about it try: import...

Thanks for your help @Andreilys, @mattFlemingTamr you need to do the following (there is actually a typo in the docs) : `c=CustomRequest(list_user_agent=user_agent, rotate_ua=True, list_proxies=None)` Nevertheless i think it won't be...

I have tried some stuff too the only thing that worked (1 year ago) was buying a pool of residential ips but now it seems even residential ips are quickly...

Thanks for your comments Indeed Linkedin has a really agressive anti scraping policy. I think LinkedIn is blacklisting the block of ips of cloud providers (Aws, DigitalOcean ...). Even for...