lebronjamesfan
Newbie
- Jul 6, 2023
- 3
- 9
I'm developing a Linkedin automation tool for myself.
Which one is safer, considering I'm doing 20 InMails/day through this:
1) Use chromedriver to log in and interact with the webpage
2) Use a chrome extension to run a content script to "animate" the process (e.g. click the message button, wait 1 second, write the message, wait 1 send, click send)
3) Use the cookie to make network requests directly (? not sure if this is even possible)
The only thing I want to optimize for is to prevent my LinkedIn from being banned.
Any insight?
My initial thought was that chromedriver would be safest because it doesn't modify the DOM. However, how can Linkedin tell that just because the DOM changed, it was due to an automation chrome extension and not Grammarly or Adblock, for example.
On the other hand, surely they could tell whether a click or typed text was user-made or automated
Which one is safer, considering I'm doing 20 InMails/day through this:
1) Use chromedriver to log in and interact with the webpage
2) Use a chrome extension to run a content script to "animate" the process (e.g. click the message button, wait 1 second, write the message, wait 1 send, click send)
3) Use the cookie to make network requests directly (? not sure if this is even possible)
The only thing I want to optimize for is to prevent my LinkedIn from being banned.
Any insight?
My initial thought was that chromedriver would be safest because it doesn't modify the DOM. However, how can Linkedin tell that just because the DOM changed, it was due to an automation chrome extension and not Grammarly or Adblock, for example.
On the other hand, surely they could tell whether a click or typed text was user-made or automated
Last edited: