Agreed, publicize and markdown are great additions. However, if I publicize to twitter from a CPT there seem to be problems with accessing the post from the shortened address in the tweet - it has https and I get messages from browsers saying they can't access because of an SSL problem (record too long). A similar tweet from a standard Post is fine and has http not https. Is there something other than setting the 'supports' to 'publicize' which needs to be added to get round this?