Yeah, I'm onboard with that plan.

I could see some future where you maybe want a split blog view (employees can comment privately, public comments publicly), but it's also hard for me to envision large corporation trusting Phabricator over Wordpress is they have super serious needs.

I'll yank it in one diff, so it's easy to resurrect.

For reference, I think this is an excellent plan and I'm stoked to see internal comments being considered. (If I already have to get my users to sign up for a Phabricator account, it's good if they don't have to also log into Disqus.)

I would also think that the comment backend is maybe something that should be configurable per blog, rather than per post. In the post, an option to enable comments - "Enabled"/"Hidden" (perhaps also "Read-only") - is more useful than the poster selecting between none, internal, Facebook and Disqus. At least for my users, I'd like to set up the blog once and then let them use the blog's default settings for individual posts.

There won't be any configuration for comments.

Works for me!