# 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 5
# self = https://watcher.sour.is/conv/2jnhzwq
Some A hole has been trying to pull every single Twtxt feed that existed/still exists since forever. How do I know? Welp' They've been querying my Timeline™ instance for all of it, every single twtxt file and twt Hash they can find. 😆🤦 It must have been going on for days and I have just noticed... + it's all coming from the same ASN AS136907 HWCLOUDS-AS-AP HUAWEI CLOUDS
> Thank you Huawei for the DDos you sons of Glitches!!!
@aelaraji Haha 🤣 I'd say it's just yet-another-bad-bot 🤖 I've blocked a lot of such bots and often their entire networks (ASN) 🤦♂️
@aelaraji Ugh, similar thing with bots (ai and crawlers) over here.
@aelaraji Ugh, similar thing with bots (ai and crawlers) over here.
@prologic This shi_ is as fun as it is frustrating! 😆 the bot is poking at me from a different ASN now, Alibaba's.
1) Short term solution: I've geo-locked my Timeline instance since I'm the only one using it (and I only do so for reading twts when I'm away from terminal).
2) Long term: I took a look at your Caddy WAF but couldn't figure things out on my own; until then, I'll be poking at Caddy-Defender, maybe throw in a Crowdsec for lols... #FUN_