social media – Page 2 – Just thoughts

Well … what a day in social media world I had yesterday!

At an unearthly hour of the morning I received a text from my son to say that he always read my blog posts because even though he might not understand them – he always felt that he ought to, just in case there was something he could actually TALK to me about … rather than just converse via Google+ (we live approximately half-a-mile away from each other)!

This was then followed by a Google+ comment from my sister – also before I’d fully woken up, and finally my wife (away for a few days) who wondered what was happening to her Google+ app on her iPhone which was being bombarded by posts from me.

By this time I’d observed for myself that for some bizarre reason, three really old posts on an old blog were being published to Google+. Why? How? I couldn’t see to the problem immediately – I had to give DJ a lift to the airport. Then I had to attend to a central heating problem and then, to cap it all (and by the time I’d sat down) – the broadband was down and wouldn’t be up until the afternoon, meaning I wouldn’t be able to do more than sticking plaster stuff on the blog until I could get full access. So I just disabled any plugin that could in any way be associated with Google from this blog and deleted all the posts from Google+, put up an apologetic post and hoped I’d arrested the flow of “spam” posts.

I hadn’t 🙁

By the time I got the broadband back it had become obvious that the problem lay with my dormant former “Just thoughts …” site and by now, exasperated and fed-up with deleting Google+ posts I took the nuclear option and just nuked the site! It’s gone, no more, I’ll get a proper redirection in place as soon as possible but for now all you can see is a simple index.html file – diharrison.com is no more 🙁

What caused all this heartache? I don’t think I’ll ever know … what I needed was access to Brainy Smurf to provide all the answers. Was it an out-of-date WordPress installation? Was it a change in a Google+ API? Was it just Friday 13th? I don’t think I’ll ever know. Certainly not now, as the website has been sent to the Room 101 of websites where all redundant and unneeded websites should go. I sent a follow-up apologetic post.

A while ago, I posted on revising my blogging strategy and the need for simplification. I think I need to review this yet again.

Why the Smurfs … I think you need to ask a couple of great friends that question.

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 🙂