# 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 6
# self = https://watcher.sour.is/conv/mgmtiha
@prologic Huh. I don’t really know how Cloudflare works, never used it. I assumed that the main use case is something along the lines of Anycast (they pick a proxy/cache close to the client). Do I understand correctly that you mainly used it for TLS termination? 🤔
@prologic Huh. I don’t really know how Cloudflare works, never used it. I assumed that the main use case is something along the lines of Anycast (they pick a proxy/cache close to the client). Do I understand correctly that you mainly used it for TLS termination? 🤔
@prologic Huh. I don’t really know how Cloudflare works, never used it. I assumed that the main use case is something along the lines of Anycast (they pick a proxy/cache close to the client). Do I understand correctly that you mainly used it for TLS termination? 🤔
@prologic Huh. I don’t really know how Cloudflare works, never used it. I assumed that the main use case is something along the lines of Anycast (they pick a proxy/cache close to the client). Do I understand correctly that you mainly used it for TLS termination? 🤔
@movq I was using Cloudflare primarily for 3 reasons: 1) For hosting DNS records 2) For reverse proxying into my infra's services and 3) As a layer of defense against DDoS attacks or stupid misbehaving bots. I'm still using Cloudflare for 1) but 2/3 are now done entirely by something I've built myself (_and working well_). Turns out in order to have decent analytics (_metrics, stats, etc_) on traffic, you have to pay Cloudflare $20/month. That's fine, and I did/do that for twtxt.net. But, if you want to know the originating IP address of requests, that's an "enterprise" feature and that'll cost you $200/month 😱
@movq I was using Cloudflare primarily for 3 reasons: 1) For hosting DNS records 2) For reverse proxying into my infra's services and 3) As a layer of defense against DDoS attacks or stupid misbehaving bots. I'm still using Cloudflare for 1) but 2/3 are now done entirely by something I've built myself (_and working well_). Turns out in order to have decent analytics (_metrics, stats, etc_) on traffic, you have to pay Cloudflare $20/month. That's fine, and I did/do that for twtxt.net. But, if you want to know the originating IP address of requests, that's an "enterprise" feature and that'll cost you $200/month 😱