# 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 13
# self = https://watcher.sour.is/conv/pdewrka
Not sure how this can be applied for self hosters?
Not sure how this can be applied for self hosters?
@prologic I think the same way the do DNS proxy. They clean all traffic for you, and your self hosted infra gets it.
DISCLAIMER: I donβt use CloudFlare other than as a Domain Registrar, and their DNS. I might be saying wrong/utterly inaccurate things.
@bender What I mean is: without using or relying on Cloudflare!
@bender What I mean is: without using or relying on Cloudflare!
@prologic oh, then it canβt be applied to self-hosters. Unless they spin up a similar-to-CloudFlare infrastructure. π
@bender I think it's the massive data analytics and machine learning that allows them to distinguish these fake bots π€
@bender I think it's the massive data analytics and machine learning that allows them to distinguish these fake bots π€
@prologic I don't know if there is/will be a Crowdsec bouncer to handle something like that. π€
@prologic that, sure, it is a determinant factor, I agree.