Hide Trackbacks is a WordPress plugin that hides pingbacks and trackbacks from your website comments.
I've updated the plugin to indicate it works correctly with WordPress 4.2.
@manton on iOS I can only post after attaching my WordPress blog even though I have a micro blog via Kickstarter?<p>#status #status</p>
I'm really impressed with the @WordPress theme customisation UI from within the product.<p>#status #status</p>
<a href="https://wordpress.org/plugins/character-countdown/">Character Countdown</a> is a handy WordPress plugin if you want to post status updates from your site to Twitter.<p>#status #status</p>
The more I think about modern blogging; the more I think the out of the box concept WordPress et al presents us is outdated.<p>#status #status</p>
Manton Reece has been having very interesting discussions about microblogging and content ownership recently. He's working on an unannounced project in this area and I've been following his progress.
A few days ago he wrote a post about Microblogging with Wordpress in which he describes most of the process of writing your status updates on your own blog first. As I had to adapt his process for it to work with my configuration of WordPress and as I am using Twitter instead of App.net I thought it would be useful to detail how I went about, based on Manton's write-up.
In order to post only the status updates to twitter, we have to identify them in both WordPress and for IFTTT.
In Wordpress, if you do not have a category for status updates, create a Snippets category (with the slug snippets). Note the category ID. In addition, create a new category called ifttt-status if you plan to post to Wordpresss from your mobile device later, as I did (this is a workaround to allow WordPress to convert from this category to the status post format).
With the category ID, we can now create a new feed by editing the .htaccess file in your WordPress installation directory, see my gist comment on manton's configuration. I had redirection issues with Manton's original setup so I amended it. What we do here is create two endpoints, one for posts without status updates (rss.xml); and one for only status updates (snippets.xml). We then point any requests to /feed (the default WordPress endpoint) to the first endpoint.
Update (26 June): I updated the gist comment after identifying issues in initial configuration. Please reread the gist if you had problems using the initial configuration.
Now create a new recipe that is triggered from the snippets RSS feed, with the action to post a tweet with the tweet text EntryContent.
You can now blog from WordPress to twitter (just leave the title empty).
I'm using DoNote to post to IFTTT which then posts to WordPress.
Login to your WordPress blog and in the users section create a ifttt user with the role of Author (this allows the user to create posts).
Install the "IFTTT Post Formats & Post Types" plugin, it will convert posts with the ifttt-status category to the status post-format. It will also hide the ifttt-status category from showing up in your template for example.
Back in IFTTT, In the My Recipe's DoNote section, create a new recipe for WordPress (you might get asked to provide the WordPress username and password you created for this purpose) with the action to create a post with the following values:
You are not limited to using DoNote if there is a trigger for your service, and you are not limited to usin IFTTT at all if there are WordPress plugins for your status update service and WordPress support for your writing app, but these will require similar configuration as detailed in this post.
Hope this helps!
I've switched this site to HTTPS, a secure connection, using a ssl proxy service provided for free by Cloudflare, for reasons. Let me know if you come across any issues.
For those using WordPress, changing the settings Site Address and WordPress Address to HTTPS may make your site unavailable. FYI, the solution I settled on is to install the WordPress HTTPS plugin. Then I set the Site Address to HTTPS. Finally, I cleared the cache. All is working fine now.
I've moved away from Cloudflare as my DNS provider and as a side-effect this means I'm no longer HTTPS for now. Sorry.