Improvements:
- Node.js updated to version 15.14.0
- Added the ability to solve Google ReCaptcha v3 as a new scraper
Util::ReCaptcha3 - In
SE::Yandex, as well as in some other Yandex scrapers, processing of the new Smart captcha is implemented - Added scraping mode via Chrome to
Rank::MajesticSEO - In
SE::DuckDuckGo languages and regions are updated - In
SE::Google::Cache added the ability to use recaptch solving services - Added collection of links to the channel in
SE::YouTube - Updated the list of languages in
DeepL::Translator - In
SE::Bing, when a ban is detected, the proxy is banned by the scraper instead of a simple change - In
Shop::Amazon the user-agent has been updated, due to which the performance has increased
Corrections due to changes in the issue:
- Many adaptations
SE::Google and SE::Yandex to changes in the layout of pages with the issuance - Fixed permanent ban of requests in SE::Google::Cache and SE::Bing
- Fixed pagination pass in SE::DuckDuckGo
- In SE::Youtube, the calculation of the number of results and determination of the existence of the next page has been fixed
- Fixed splitting into blocks of large queries in
SE::Yandex::Translate - Fixed SE::Bing,
SE::MailRu, 
SE::MailRu::Position, 
SE::Google::Compromised, Rank::MajesticSEO, 
Rank::KeysSo, 
SE::Yandex::Direct, 
SecurityTrails::IP, 
Net::Whois, 
SE::Bing::Translator, SE::DuckDuckGo, 
Social::Instagram::Profile, 
Shop::Yandex::Market, 
Rank::Ahrefs::KeywordGenerator, 
Rank::Ahrefs::KeywordDifficulty, 
SE::Seznam, Shop::Amazon, 
Rank::Linkpad
Bug fixes:
- Fixed a bug in
HTML::LinkExtractor that caused scraping on request to stop with an error - In
Rank::MOZ, the absence of retries has been fixed, and the logic for detecting unsuccessful requests has been changed - Fixed proxy check error if the password contained "*"
- Fixed a bug due to which Check content stopped working when using the template engine in Additional headers
- Fixed logic for checking results in
SE::Bing::Images - Fixed XPath
- Fixed memory leak: during long run the node.js process gradually filled up all available RAM
- Fixed work with proxies on some sites, the bug appeared in one of the previous beta versions
Last edited by a moderator: