Automate everything

User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:capmonster:changelog [2019/11/19 09:18]
deemer [CapMonster (12.11.2019)]
en:capmonster:changelog [2019/12/13 12:05] (current)
deemer [CapMonster (19.11.2019)]
Line 1: Line 1:
 +====== CapMonster (13.12.2019) ======
 +[+] An opportunity to save profiles from reCAPTCHA via the Chrome engine was added. If a reCAPTCHA was solved successfully,​ then the profile is saved for further use. This decreases the possibility of getting banned and increases acceptability of tokens. The profiles are mutual for versions 2 and 3, a profile, which has worked on solving reCAPTHA 2 for several days, gives more high quality tokens for reCAPTCHA 3.\\
 +[+] reCAPTCHA CPU consumption via the Chrome engine was optimized.\\
 +[+] Improved the acceptability of reCAPTCHA tokens.\\
 +[+] Anti-–°aptcha protocol support was added for solving reCAPTCHA 3.\\
 +[+] The amount of captchas being solved at the moment is now displayed.\\
 +[+] A method for receiving information about the CapMonster load http://​​80/​getcmstatus \\
 +was added. The result is returned in the following JSON format:\\
 +{"​CpuLoad":​3,​ "​RemoteRunningSlots":​0,​ "​RemoteTotalSlots":​80,​ "​Rc2TasksWaitingInQueue":​0,​ "​Rc2InstancesRunning":​0,​ "​Rc2InstancesWithTask":​0} If protection is enabled, it is necessary to pass a key getcmstatus?​key=blablabla\\
 ====== CapMonster (19.11.2019) ====== ====== CapMonster (19.11.2019) ======
 **New:**\\ **New:**\\
en/capmonster/changelog.1574155109.txt.gz · Last modified: 2019/11/19 09:18 by deemer