Hi all, We’ve been heads down on the internal beta, getting ready to open this up to everyone on Monday, April 6. We’re feeling very good about where things stand and are excited to let you kick the tires.
As of now, the schedule remains:
-
Public beta: April 6
-
Full launch: April 14-15
So yes, this thing is actually happening!
The full launch could slip if major issues surface during the public beta, but at this point we’re confident we’ve already caught any real showstoppers. What remains is edge-case work: bugs that affect a small number of users or show up in situations we didn’t anticipate. That’s exactly why the public beta matters.
Your Community Advisory Panel has already been putting the site through its paces, and their feedback has been invaluable. Staff and I simply don’t use the site the same way many of you do. More eyes means better outcomes, and thanks to their work, you’re getting a more polished product for the public beta than you otherwise would have.
A few notes:
- I’ll be out of the office April 15–21, right at launch. Not ideal, but this trip was planned over a year ago and the timing just landed this way. It’s a silent retreat—my first real digital detox in two decades. I’m aware this will invite jokes about me hiding from reactions to the new site, but I have full confidence in our product and community teams to manage the transition. I’ll be back rested and ready to engage.
- In the meantime, you’ll be hearing a lot from Iterology, Allison, and Minos. They are far more fluent in the details of this transition than I am. Allison and Iterology are leading on the technical side, and Minos is heading up community. Please treat them with respect—they’re doing the work to make this successful. If you’re frustrated, direct that at me. I can take it, especially zen’d out after my silent retreat!
- Don’t miss Minos’ recent postings on site credentials, and what content will be migrated, and what won’t. All important site updates will be republished to the Announcements group.
- On transition day, the site may be down for up to 24 hours. That time is needed to migrate final content, verify stability, and complete the DNS switch—essentially pointing dailykos.com to the new infrastructure. Not fun, but necessary.
This is a complex transition. Some rough edges are inevitable. But what’s on the other side is a modern, secure, and stable platform—and over the next year, we’ll be building on it with features we simply couldn’t support before.
I’m excited for what comes next.
Previous updates:
