KelloggBot

It looks like this script is using the standard Faker module email generation, which will generate email addresses exclusively with domains at example.net, example.com, and example.org. It also attaches the exact same .png [0] for the resume in every fake application. So these should be pretty easily filterable based on those 2 facts alone. Additionally, there are plenty of red flags that any human reviewer would quickly pick up with these applications. The addresses don't exist. The random prior occupations it submits are rarely in line with what you'd expect for these positions. The name generator is pulling random first names for the last name as well. And the randomly generated email addresses contain names that don't match the name on application. So, the script will submit an application for "Susan Justin," a former Surgeon with th

> Can you be more clear on this? I don't see where this is happening. There's a start_drive function that they call once in main and use that reference the entire time. https://github.com/SeanDaBlack/KelloggBot/blob/main/req.py#L... They run start_driver() inside a while loop with 10000 iterations > How else would you get around navigating the DOM which this has to match precisely? For that specific one I'd probably try "//*[contains(text(), 'Apply now')]", if they add a single element to that page the entire xpath will fail in the code example > Very subjective? Do you have two first names? > Agree with this but maybe it's not possible for some reason in regards to how the webpage is configured? Maybe! Still, I bet you it's possible to wait for an element even if it's your own action taking effect.

>Can you be more clear on this? I don't see where this is happening. There's a start_drive function that they call once in main and use that reference the entire time. >https://github.com/SeanDaBlack/KelloggBot/blob/main/req.py#L... the call to "start_driver" is inside the "while (i < 10000)" loop

- Opening and closing the driver 10000 times Can you be more clear on this? I don't see where this is happening. There's a start_drive function that they call once in main and use that reference the entire time. https://github.com/SeanDaBlack/KelloggBot/blob/main/req.py#L... - Complicated flakey in-line xpaths '//*[@id="content"]/div/div[2]/div/div[1]/div[1]/div/div/button' How else would you get around navigating the DOM which this has to match precisely? - case first_name | last_name both uses a first_name() generator, should just be generate_name() Very subjective? - Time.sleep(x) is flakey, you should wait for the element to appear. Agree with this but maybe it's not possible for some reason in regards to how the webpage is configured?

It's actually well written, rather pretty code. https://github.com/SeanDaBlack/KelloggBot/blob/main/req.py Edit: The code is not PERFECT as MANY people have picked it apart below. But if I had to work with this code on a daily basis I would certainly not mind. If you ever need a code review just post your code on hacker news and say it's well written....

https://github.com/Heroin-Bob/Kellogg-Time-Waster-3000 shows a 404 but https://github.com/SeanDaBlack/KelloggBot looks like its still up for now yea... why would they use their real name haha