In reply to: Intertextrevolution
Thanks for the kind response.
I’ll answer here your webmention reply didn’t show on my site. I’m sure I probably have a setting for that wrong somewhere. 🙂
You are right, WordPress is a handful to get set up. If you add in the Indieweb stuff it becomes even more of a handful. In theory you only have to do this once which is good. You folks are on the right track with the Indieweb plugin – it makes things much easier. All I knew, after doing a lot of reading on Indieweb stuff, then seeing the Webmentions on other blogs, I knew this was what I wanted.
After writing that post I got to thinking: one approach to documentation is to treat it like cooking recipes and cooking classes. (ie. I’m making a pie crust, the recipe calls for peanut oil which will do this, but can I substitute corn oil and what will that do to the pie crust? etc.)
Another way is to think like a blogger: “3 Best ways to Syndicate Your Indieweb Blog to Twitter,” type articles.
I understand the Indieweb eco-system is not yet complete, templates, feed readers are all still being developed. Someday, this will all be close to plug and play, but in the meantime we need some big FAQ’s and comparison of real world (read WordPress for now) services. Unfortunately, my trial and error approach burns up too much time.
Thanks to Chris Aldrich who has been doing a good job of explaining a complex eco system.
What the Indieweb really needs is some practical, plain language documentation to lead end users through the forest of plugins, jargon and bailing wire setups to get the mainstream blogger to the promised land of Indieweb goodness.
Example: If I use Jetpack to post to Twitter, will that give me all the same Indieweb Webmention, commenting type goodies as using Brid.gy? If not, what specifically won’t work?
It’s all fine to say “Install this and don’t worry” but then Bridgy suddenly breaks and won’t post to Twitter. What then? Will Jetpack do just as well?
And what about G+?
I know some have been diligently trying to provide guides to this stuff but there are problems.
- To many links in the chain. Weakest link breaks, then we have a Scudhunt trying to find which link is broken.
- There are X number of ways to syndicate (crosspost) content. What are the strengths and weaknesses of each way?
- Indieweb plugin by plugin practical guides for WordPress. Like the problem of empty Titles on microposts and WordPress wanting to assign a number as the title. Getting around that.
- What works best for what.
- Don’t send me to Github. That’s for developers. You don’t want the general public bouncing around there.
The point is if the Indieweb is ever going to grow beyond a small niche thing for developers it really needs some refining, documentation and streamlining. Their goals are noble, their efforts worthy but barriers for broader adoption do exist. And we are hitting those.
With the IndieWeb Summit coming up at the end of June in Portland, David Shanske and I discuss it, participation, and other parts of the IndieWeb community.
Source: An IndieWeb Podcast: Episode 5 “Indieweb Summit and More”
Here is the current syndication scheme from this blog:
Micro.blog via RSS
Twitter via Brid.gy plugin, I’m not totally happy with the way posts are formatted on Twitter but I think Brid.gy is facilitating 2 way communication with Twitter so I like it for now.
Mastodon.social via Mastodon Autopost plugin.
G+ via WordPress Jetpack syndication.
WordPress.com Reader – I should mention this. Even though this blog is not on WordPress.com it must be automatically syndicated on the Reader there because I’m getting traffic, which is nice! There are definitely eyeballs there.
Facebook via WordPress Jetpack syndication – while I think Facebook is toxic, the only way I can show friends and others that there are alternatives to it is to post there. So I reluctantly turned FB syndication on. Worth trying.
Purpose: this post is mainly to remind me of how I currently have things set up.
This article inspired me to install the Post Kinds plugin for WordPress. This is a reply. I have no idea if and how this works but I reckon Chris Aldrich will forgive me for experimenting. Let’s see if it works.
Thinking of converting your WordPress blog into an Indieweb compliant instance? Setting up a new install of WordPress is complicated enough as it is and making your blog work in an Indieweb manner can sound – complicated. Fear not, there is a pretty easy way: Indieweb WordPress Plugin. This plugin is really all you need to get started. It will gently lead you through the steps of finding specialized plugins that make the Indieweb stuff happen. It just makes the whole process easier.
I am still going to give this an Intermediate skill level. If you are a complete beginner to WordPress, get to know the basics of your WordPress control panel first and also blogging basics, then worry about the Indieweb stuff later.