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 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.

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.

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.

Most of today has been completely unproductive. I spent the majority of it fighting with Instantbird, (which is not so instant), which I use for Slack, which we use for WordPress Core contributions and other WordPress bits like WordPress accessibility, and other sub-projects. I spent several hours getting conversations to appear and allow me to interact with them. This is text-based chat, so you’d think everything would just work. I finally got everything up and running just before the weekly WordPress accessibility meeting. So by 3PM, I was pretty much done.

And then, I decided I wanted to listen to some of the content that’s on my USB drive. My network attached storage is dead, and this serves as the backup for most of that content. I have music that’s not available on Spotify, or, if it is, it’s “digitally remastered,” (which in most cases actually means re-recorded by the original artist, except now they’re older and they’re showing their wear and tear), plus some audio dramas and books that aren’t on Audible.

Yay time to screw with Windows homegroup settings. Two different versions of Windows on two different PC’s, and the one with the big speakers connected to it is by my bed, as it should be. Well, Windows has never been great shakes at either networking or permissions, (See also: Windows PC versus Windows Vista), and so unless you have a crossover cable, that’s long enough, (I don’t), or you want to make things more complicated and use one computer as a pass-through for network traffic, (I don’t), it’s homegroup configuration time. This is usually straight layout tables all the way down, and will usually take up much more of your time than you’d like, and require several beers to get the entire job done.

So I set to work. Shared the drive properly, set the permissions, then went to access it on the PC by the bed. “Network path not found.” OK then, time to start digging. Make sure I have the homegroup password correct, (I didn’t), get all the names correct. In networking, names are very important. PC’s/devices are not like your hookups. Forget their names and you’re done. So I get all that correct, in less than an hour, and, we have content delivery.

And that’s Monday in the bag.

I think I may have made a promise to myself at some point that there would be no code on this blog.

Well, promise broken, because I want a place to document my side projects.

My current fascination has been with metadata.

In a nutshell, metadata is the information that gets collected when you do things like take pictures with your phone. It can be information like credit, shutter speed, or location, if you have enabled location services for your camera app on your phone.

Basically, everything you do has metadata attached these days. Photos aren’t the only information with metadata attached. Photos are just the best example I can come up with that’s not too far out there in geek world.

So, I have started playing around with displaying this metadata. What if I could take the information from photos for instants, and use it to plot a location on a map. Then display that map so the people who read this blog could then look at where I am, or where I was when I wrote a particular post at least?

So far, I think I have the location part working. If you look at this post, under the content, you should have the ability to hover over the location and see a street level view.

It’s not perfect, and it’s not exactly the way I want it, so I will continue playing around. And of course, I will document the whole thing here, complete with code examples.