Am totally into CSS backgrounds with partial transparent color overlay in the element above. Nicely ties the palette together. #
Slack users: do you setup channels per project or per content type (build; errors)? #
Interrupting ads are as bad in games as they are on websites. #
Experiencing “Slack and the case of the missing emails” #
Updated my microblogging .htaccess gist so if you used that yesterday please try again. #
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.
- A theme that supports post-formats.
- an IFTTT and Twitter account.
- A self-hosted WordPress installation, hosted using Apache.
- (optionally) the DoNote app from IFTTT for your mobile device.
Step 1: Link a status updates feed to Twitter
In order to post only the status updates to twitter, we have to identify them in both WordPress and for IFTTT.
Create a dedicated category
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).
Setup the RSS feed endpoints
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.
Post new status updates to Twitter
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).
Step 2: Post status updates from your mobile device
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.
Link DoNote to WordPress using IFTTT
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:
- Title: (leave empty)
- Body: NoteText
- Categories: Snippets,ifttt-status
- Tags: (leave empty)
- Post status: Publish immediately
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!
My status updates are now published to my own site first. #contentownership #