[bisq-network/roles] DNS Admin (#18)

[cbeams]

Update: I've just re-enabled Cloudflare proxying in front of the bisq.network site. We got a bill from Netlify for the first time last month (March 2022), and after following up with them and looking at traffic data, it's because there was what looks like an attack on March 21st and 22nd resulting in 22M+ requests in a single day totaling nearly a TB of data transfer. @ripcurlx has paid the bill and will request reimbursement for it similar to the way he requests reimbursement for GitHub fees. I'm still waiting for Netlify support to tell us if there's anything we can do to avoid such spikes in the future, but in the meantime, I've re-enabled Cloudflare proxying for bisq.network in hopes that Cloudflare's DDoS protection might help mitigate any such future attacks. I see no practical downside in doing this, and the change is easy to reverse (to remove the proxying) if anything does come up.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/18#issuecomment-1097807082
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/roles/issues/18/1097807082 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220413/ffee106c/attachment.htm>