David Shanske has added location support to his site, complete with an open street map and the location name as a link. I’m eager to try it out and his releasing this reminds me to finish my own location support. I have the fields created, but I’d still like to get WordPress to automatically pull in the location associated with the browser, so that when I post from my phone I can effectively replace checking into Facebook or Foursquare. Foursquare’s cute for the points but that’s about it. I’ve copied this site over to staging so I can make code changes and tweak until I’m happy, or at least until I have something I can live with, until I decide to tweak again. The curse of being a developer, I suppose.

I’ve been spending some time browsing through this list of posts about the indieweb, and I came across this post that details how the first loosely-federated comment thread got started. By loosely-federated, I mean there was no closed platform involved, (*cough the Facebook*), nobody had to follow anyone to interact, people just read something, commented on their own sites with their software of choice and it all worked together beautifully. This is how the web is supposed to work, and it proves that we can have social media without handing all our stuff over to someone else so they can make money off of it by building their advertising network on top of our stuff, (baby pictures on Facebook, anyone), and then not allowing us to consume the content we create however we want. It’s really cool to see this kind of thing in action. It’s one of those things that you know on a theoretical level at least if you develop for the web. But seeing it actually work is so cool. The original post seems to have disappeared, 😉 and it would have been cool to see the swarm in action. But still, the potential here is amazing.

As I was scrolling through Twitter this morning, I came across a recommendation in favor of Press Forward, a free software alternative to closed-source tools for journalists that can also act as a self-contained RSS reader and Instapaper/Pocket replacement for use on WordPress-powered sites. The above is to provide context for those who haven’t been following this conversation. Plus, I’m still figuring out this crafting replies on my own site thing.

Anyway, I received some very helpful feedback from the author of the original post regarding my current installation, which included a link to the project’s Github. This is great, both because I’m really looking forward to using this since I really don’t like messing around with Pocket/Instapaper due to their accessibility issues, plus owning your bookmarks. So far the only problem I’ve found, other than the issue mentioned in the feedback, is one where the bookmarklet cannot be accessed with a keyboard. You have to use a mouse. So I’ll be filing an issue, and hopefully a pull request, because along with the Indieweb implications and uses for this, it also presents a great alternative for controlling the display of the lists of links we collect, allowing for the creatin of accessible user interfaces.

Also, Twitter’s 140-character limit is extra frustrating when you realize that you can reply to tweets from your own website, not be stuck trying to fit things in 140-char chunks, and keep ownership of the content, which is why I replied here. I need to finish getting customerservant.com switched over to a theme with complete microformat/microformat 2 support, and am looking at how to do this with the Genesis framework if possible.