Migration of Dreamwidth off of Cloudflare

[mark]

Good $time_of_day!

If you're just joining us and are not sure why we're moving off of Cloudflare, please see denise's previous post. I know that as of today, Cloudflare has decided to suspend service to the site in question, but we have decided to continue with our plan here and end our relationship with them.

I'm going to give a technical update here. Comments are screened, mostly because I won't be around to manage them overnight, but we'll look and unscreen things tomorrow.

As of a few minutes ago, we have completed the bulk of the migration. We are no longer proxying any user content through Cloudflare for the main Dreamwidth service. I.e., if you're reading this, your browser requests are no longer going through Cloudflare anymore.

The remaining work to be done before we're no longer customers of Cloudflare:

• Move our domain names and DNS serving. This is going to take a week or two, as DNS changes are not super fast and they're very important to get right.
• Move development services (the DW Hack domain names and such.)
• Cancel and close our account. (Will be done as soon as the above two are done.)

Additionally, there is going to be some ongoing work to tune the system. The reasons we had moved to Cloudflare in the first place were because, frankly, they do provide a technically excellent solution for deflecting automated traffic (bots and things), a robust cache, and they helped us save a good bit of money.

We are likely going to see some intermittent issues while we work to achieve some amount of parity back on the older system. I apologize in advance, and we'll use our dreamwidth account to keep you posted when there are issues, so please check that out.

Anyway, feel free to drop any questions in the comments and I'll get to them in the morning. Thanks again for your patience while we move things around.