- Me
- People or bots looking for vulnerabilities
- Web crawlers
with about 0.5% of traffic being legitimate, not-me visitors.
# 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 12 # self = https://watcher.sour.is/conv/4xxgkfq
HELP
, because my quickly thrown together parser didn't expect this sort of crap. Any particular tools you use to analyze your logs with?
grep
and a text editor. @adi wrote a suite of command line tools for analyzing different web server log formats if you're interested: fl, cl, and cbl
grep
and a text editor. @adi wrote a suite of command line tools for analyzing different web server log formats if you're interested: `fl`, `cl`, and `cbl`
grep
and a text editor. @adi wrote a suite of command line tools for analyzing different web server log formats if you're interested: fl, cl, and cbl
grep
and wc
cbl
and friends. When I quickly counted by HTTP status code, I thought it would be nice to interactively drill down further. But I couldn't answer my question of what I actually want to see or look out for, so I stopped.