| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
+ add ability to define a custom time period
This feature enables users to further narrow the expected query result by customizing the time period.
Every script feature is able to handle the custom timestamps, but beware no further consistency checks are done. Thus if you provide a stop timestamp that is prior to the start timestamp the output will be empty, no error whatsoever.
Timestamps must be conformal to the Python [datetime](https://docs.python.org/3/library/datetime.html#strftime-strptime-behavior) module. The easiest way to achieve that is to use the ISO-8601 format from the unix date function:
```bash
$date -Ins -d "3 weeks ago"
$date --iso-8601 -d "3 weeks ago"
```
|
| |
|
|
|
|
|
|
|
|
|
| |
+ add time-borders to all queries
The JabberSpam manifesto states that the critical period for a server to be approved again is 14 days. Thus I adjusted all queries required for the report function to only count within these borders.
Though if a domain is specified without the report argument the time border is increased to 1 month to increase visibility.
misc:
+ add Codefactor badge
|
| |
|
|
|
|
|
| |
* add more docstrings to main.py
* add README entry for no argument
Thanks to @weiss
|
| |
|
|
| |
* update README to explain config.py
|
| |
|
|
| |
* update README.md to the latest changes
|
| | |
|
|
|
+ python3 ingest and db management
+ abusereport bash script
|
