I have had a web presence since about 2001. Initially, I set up a blog using Radio Userland but quickly abandoned that when Google launched Blogger. I then jumped to Tumblr then back to Blogger. But it wasn’t until 2005 that I finally registered a domain, islandinthenet.com, and started hosting my online presence, my “house”, on WordPress.
One of my favorite IndieWeb quotes thus far, and certainly a sentiment I’ve had many times:
I visited the IndieWeb wiki and went down a rabbit hole of information. As I read, I kept nodding my head, “Yes, we need this. I have to do this.”
Khürt also highlights another good reason for IndieWeb:
Each time Instagram changed their terms of service to something with which I disagreed, I would delete my account. I am on my third Instagram account. I have a lot of image posts with missing content.
Despite some of the problems people have in getting some IndieWeb technology to work the way it could, I’m very heartened by people like Khürt Williams who see the value of it to the extent that they’ll struggle through the UX/UI issues (which are ever improving through the herculean efforts of so many in the community) to make it work for them.
Since Khürt may not be following developments as closely, I’ll briefly mention that the overhead involved for owning your Instagram posts and FourSquare/Swarm posts is coming along with efforts like Aaron Parecki’s OwnYourGram and OwnYourSwarm. David Shanske has been working diligently on updating some of the workflow for the Post Kinds plugin to work better with checkins and locations for FourSquare/Swarm. For WordPress specific users who want an alternate Instagram option that uses a PESOS syndicaton/ crossposting model, I’ve also found some excellent results with the DsgnWrks Instagram Importer, which provides a bit more WordPress specific data and integrates wonderfully with David Shanske’s Simple Location plugin.
I’m hoping that Michael Bishop’s idea of doing weekly updates on WordPress specific IndieWeb updates will help those who are interested in keeping up with movement in the community without needing to read the chat logs or GitHub updates regularly.
As for the issue of Akismet spam and Webmentions, this is a known problem that Akismet is aware of and hopefully working on. In the meantime, there’s a documented work around that will fix the issue that has (in the practice of several hundred people using it) an exceedingly low rate of allowing spam through.