A change of Google+ posting strategy

I posted this on Google+ to earlier today, and +Simon Wood (@MrSimonWood) suggested I owed it to the twitter community I used to be so active in, to explain where I’d been, and what and why I’d decided to change my Google+ posting strategy that might mean that links to some of my Google+ posts appeared more regularly on twitter. So here’s what I wrote earlier today to the Circles that I post to on Google+. I hope it makes sense. I also hope you don’t mind me hi-jacking “Thought grazing …” for the purpose – again it just seemed the best place to put it.

We ought to have another meet-up at Costa Coffee soon … shouldn’t we?


A change in Google+ direction today for me, so please excuse this post which explains what I’m doing, and why.

My main use of Google+ since it started has been as a platform for targeted postings to Circles – I have many which align with my interests and relationships. Some intersect, some are discreet. When you have quite a few circles (as I have) they’re difficult to maintain and even more difficult to select from, for a targeted post. My strategy has been successful however, I feel, and a few of my circle members are now active users of Google+.

Using such an approach has seen my use of twitter decrease significantly – there’s only so much social interaction you can engage in – but I’m very aware that whilst I’ve enjoyed being part of the new Google+ ecosystem, I shouldn’t have turned my back on twitter as much as I had with Facebook, for which I make no apology for my desertion.

So from today, whilst not changing the way I use Circles and Communities – which really works and provides “safe” places for conversations, I intend to do more Public posting to Google+ all of which will be picked-up by ManageFlitter and tweeted. Hopefully, this will also encourage more of my friends, contacts and acquaintances to become active in Google+ as well. I will have a purpose to look-in on twitter more often as well.

For this to work, I’ll have to make sure the first 100 characters or so of my Google+ post concisely explains the content. A link to the Google+ post will be provided in the tweet, which will lead the reader into Google+.

So to you my Google+ readers … your feed from me may become a little “noisier”. Either turn the volume from me down, or just ignore posts that you’re not interested in. I’ll see how it goes – I’ll be interested in your feedback.

Getting Spotify to work for me !!!

Creating a shared Spotify Playlist that I can blog about has taken me much longer than I ever expected or hoped it would. I’ve had to learn a fair bit about sharing music, which I didn’t know anything about, and even more about what you can do with Spotify and how it can be made to work with iTunes. A certain sense of satisfaction at having got it to work, but I’d be the first to say that “there must be a better way” and if anyone can suggest it, I’d be grateful.

You start off with the service that does just what you want it to – create a Playlist and then Share it with whosoever you want to share it with, be it Public, or Limited. That’s fine … there’s a bit of a setback when you realise there’s not an easy way of importing the actual Playlist into a blog, so you have to go back to iTunes (where you created it, before importing the track list into Spotify) and saving that Playlist as a text file. This you then have to edit substantially to get any text for the Blogpost.

Then, the major setback, you find that not all the tracks on the playlist are recognised by Spotify; they are played because Spotify plays them as Local Files, but to get the best experience you then have to go through the ones that don’t have a Spotify existence and find the track manually on Spotify itself. This may be because it’s just got a slightly different name to the track on your Playlist. Bother! That will still leave some that don’t appear on Spotify at all – my opera tracks are a good example. As I said before, they play because they play as Local Files, but that won’t do if you want to create a Blogpost that references ALL the tracks on the Playlist.

So you have to create a Shared Folder that you point your readership to and ask them to download the tracks into their own Local Files folder in Spotify – which they will have have had to install on their local machine; would they bother, I think not.

Having done all of that – which is a lot of work to just read a Blogpost – it does work; but it’s not worth the effort for the Writer or the potential Reader, I’m afraid. The best solution is to “forget” about the missing files, just put it down to “c’est la vie”, share the Playlist on tumblr and enjoy the music. Perhaps reading the Blogpost alongside the tumblr stream playing in the background 🙂