-
Updated
Apr 27, 2020 - Python
scrapper
Here are 374 public repositories matching this topic...
-
Updated
May 15, 2020 - Python
-
Updated
Feb 28, 2019 - Python
-
Updated
Jun 1, 2020 - Python
-
Updated
Sep 4, 2020 - Python
-
Updated
Dec 17, 2018 - JavaScript
I get it that not all fields in an extractor have to be encoded. But I wonder if it would be bad at all to encode everything and automatically in the Extractor class. Just iterate over the object keys and encode the values. Perhaps, we can also add some heuristics to determine whether we should encode the field or not, although I am not sure there's any benefit (in execution time).
The motiv
-
Updated
Feb 21, 2018 - JavaScript
-
Updated
Aug 30, 2020 - C#
-
Updated
Jul 4, 2020 - JavaScript
-
Updated
Aug 16, 2020 - JavaScript
-
Updated
Aug 25, 2018 - Go
-
Updated
Aug 5, 2020 - Ruby
-
Updated
Jul 2, 2018 - Python
-
Updated
Nov 16, 2019 - PHP
-
Updated
May 26, 2020 - PHP
-
Updated
Oct 25, 2019 - JavaScript
it would be nice to have this, since my.telegram.org allows it
Improve this page
Add a description, image, and links to the scrapper topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the scrapper topic, visit your repo's landing page and select "manage topics."


The idea is to have an option like 3 (Do a Google search, save the Urls found and search the emails), but search a list of phrases.
This list can be in a .txt
The option can ask for number of search results in Google