-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] New scanner interface #967
Labels
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
sundowndev
changed the title
[RFC] Design proposal for v2.4
[RFC] New scanner interface
Jul 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is a RFC about major architectural changes in the upcoming next versions of PhoneInfoga.
Context
It's been a while that PhoneInfoga stopped working properly due to scraping limitations. I knew since the beginning that this project couldn't work without constant maintenance. The goal of this new version is to bring a new set of features to the existing project and stop relying on scraping to gather information about phone numbers.
High-level roadmap
That means the tool will no longer rely on free resources and the user will need to specify one or more API keys in order to use the tool. Each scanner will become optional so the user can choose which one should be used in a scan.
Usage examples :
Definitions
Backward compatibility
We MUST break as less as possible so consider the following :
Scanners
This is a non-exhaustive list of scanners we could implement in the future. Each of them still requires its own investigation to better understand how it works and how it can bring value to Phoneinfoga users. Some scanners may require a rate-limiting mechanism (e.g. Pipl).
References
Social medias: Facebook, Twitter, Weibo, TikTok, Instagram, LinkedIn, VK, Snapchat, YouTube, Periscope
Search engines: Google, DuckDuckGo, Yandex, Bing, Yahoo, wayback machine, archive.ph
The text was updated successfully, but these errors were encountered: