# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 8
# self = https://watcher.sour.is/conv/axb3ekq
So I need to figure out how to block ASN(s)...

Additionally, I' thinking of; How to detect DDoS attachs?

Here's one way I've come up that's quite simple:

> Detecting DDoS attacks by tracking requests across multiple IPs in a sliding window. If total requests exceed a threshold in a given time, flag as potential DDoS.
So I need to figure out how to block ASN(s)...

Additionally, I' thinking of; How to detect DDoS attachs?

Here's one way I've come up that's quite simple:

> Detecting DDoS attacks by tracking requests across multiple IPs in a sliding window. If total requests exceed a threshold in a given time, flag as potential DDoS.
On DDoS, wouldn’t sshguard and/or fail2ban work?
@bender Wre I'm talking about Web right? 🤣
@bender Wre I'm talking about Web right? 🤣
@prologic fail2ban should work fine.
@bender So you mean, get failtb2n to look at my Caddy audit logs for violations and then just block at the firewall level for repeated violations? 🤔
@bender So you mean, get failtb2n to look at my Caddy audit logs for violations and then just block at the firewall level for repeated violations? 🤔