I'm experimenting with a feed out of this Ode site whose sole purpose is to originate and archive my posts to social-media services such as Twitter.
Ideally I will be pointing the RSS of a specific subset of posts either at Twitter directly, or at http://dlvr.it, and the only things I will be posting to social networks will both originate and live here.
This is a "push" system that doesn't gather any responses to these social-media postings, but I could always gather and repeat that history here, provide a link to same, or just forget about it and be happy having my "original" posts contained within this portion of my Ode blog.
Later: The super long URL in the header ran right out of the box, so I used bit.ly to shorten it.
The link referenced in the title is the URL to this very entry: http://stevenrosenberg.net/blog/social/posts/2013_0220_twitter_out_of_ode
Even later: problems with this method include: The link doesn't track from the blog to Twitter. Instead the Twitter post goes back to this blog entry. That might not be so bad -- Any link I want can be at the top of the blog post, and the reader can go from Twitter, back here, then to the outbound link.
But it would be better to at least have the flexibility of originating a Twitter post with a unique link and pushing that to the social-networking service rather than a link to a blog post. There is probably some way to do this with the Twitter API (and maybe even the Twitter-related Perl modules). Something to think about.