You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.
I think this project has crossed some key thresholds recently, that have taken it from a small utility optimized for a few people doing a narrow set of things, to something that has the potential to add significant value to a wide set of use cases.
I think the domain-scan name is a bit limiting (especially if the project were to more robustly handle alternate ports and scanning per-URLs), and doesn't get at the core reasons you might use the project.
In no particular order, here's what I see as the core reasons this project is valuable:
Tight, opinionated integration with two powerful pieces of infrastructure: Amazon Lambda and Google Chrome.
Lightweight setup and footprint: no interesting compilation or daemons needed, just local package installation in high-level languages. Local parallelization uses native Python threading.
Human-friendly output: creates aggregate CSVs intended for immediate human consumption, without requiring additional ETL work.
Database- and schema-agnostic: Just drops JSON and CSV files to disk. (And this could be pretty easily modded to allow data to be dumped to S3/etc instead of disk.)
I don't think the name needs to somehow explicitly hit all these points, but I do think it should help the project stand out more and evoke its core values.
Any thoughts or ideas?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think this project has crossed some key thresholds recently, that have taken it from a small utility optimized for a few people doing a narrow set of things, to something that has the potential to add significant value to a wide set of use cases.
I think the
domain-scan
name is a bit limiting (especially if the project were to more robustly handle alternate ports and scanning per-URLs), and doesn't get at the core reasons you might use the project.In no particular order, here's what I see as the core reasons this project is valuable:
I don't think the name needs to somehow explicitly hit all these points, but I do think it should help the project stand out more and evoke its core values.
Any thoughts or ideas?
The text was updated successfully, but these errors were encountered: