New theme on LayMusic.org

[bugs]

I got a notification that there was a new WordPress version
available, so I updated my blog. This is normally a good idea,
since WordPress puts a lot of work into fixing security bugs not
too long after the hackers find them.

In this case, it turned out that my theme was incompatible with
the new version, and none of the menus worked. This could
probably have been fixed, but my theme was a bit of homemade CSS
on top of a theme than hasn’t been maintained for several years,
so I decided to just go to the latest offically approved theme
and customize it.

I think what I have is inoffensive, and some time when I need a
Friday afternoon art project, I may make it better.

Meanwhile, if there’s anything from the old theme that isn’t
there that you miss, let me know, and I can probably put it back.

LayMusic.org goes Social

Me and Social Media

There are clearly people in the world who have figured out how
to follow large numbers of friends, acquaintances, businesses,
etc. on Facebook and Twitter.

I am not among them. I do check Google+ regularly and know
some nice people who occasionally post there, but if there were
more of them, I would probably stop reading regularly. I want my
news and email sorted nicely into categories, so that I can get
the stuff that I really want in 30 seconds, and look at the other
stuff when I have time for it.

To that end, I read my mail with GNUS, which splits it into as many
“groups” as I care to configure based on the mail headers. I also
follow a large number of blogs and other webpages with RSS
feeds via Gwene.org.

I don’t know why everybody doesn’t do it this way, but they
don’t. I’m always talking to someone who has unsubscribed to
something interesting but not critically so because it was cluttering up they (presumably one) mailbox.

I tell people I don’t do Facebook because I maintain two
websites and that’s enough to keep up-to-date. So I keep getting
annoyed at my closest friends because they aren’t interested
enough in what I write to bother to read my blog. But of course
it’s because their lives are so cluttered with Facebook that they
don’t have time to also follow blogs.

So I caved about Google+

There are actually things it’s easier to just post on Google+
than to put on my blog. WordPress is pretty clueless as far as
just posting a picture with a short caption, and Google+ is easier to use for a
one-link pointer. So some time ago, I put a widget in my blog’s
sidebar that had pointers to my last few Google+ posts.

Then last June, one of my Google+ friends said how much she
wished my blog posts on the Boston
Early Music Festival
would show up on my Google+ feed. I
decided to experiment with this, and set up the Jetpack Publicize
feature to automatically post blog posts as Google+ posts.

Of course, this makes the blog sidebar pointers to Google+ less
useful, since often all or most of them are just pointers to the
last few blog entries. But it has led to more +1’s and even a few
comments on what I write, which the blog basically doesn’t
have.

So today, I caved about Facebook and Twitter, too

So I decided the people who are always claiming they would like
to follow me on Facebook but they don’t have time to read my blog
should have their chance. I have now configured my blog to
automatically post to my Facebook and Twitter pages.

I don’t know that I’m going to take up reading Facebook or
Twitter, but if you do, you now have a chance to read my blog if
you want to.

There’s a real wordpress python library now

I’m going to have to do some more programming to use it, but
it’s letting me set both categories and tags on these posts from
the command line.

Here’s the
documentation,
including how to install it.

I have a simple modification of my addpost.py script that
allows a tag as well as a category, but I think I’ll write a more
elaborate one that will allow pages and multiple tags and
categories.

Other plans include a script to go through and turn some of the
tags into categories, and modifying my addmedia script so that
wordpress knows the right mime type.

Then there might be a script that uploads a picture and a post
about it and including it with one command.

Programming is wonderful.

I’m Back

If there’s anyone there who got interested in the blog back in
2010 when I was writing a post a day about whatever interested me
that day, you’re probably bored by the way it’s been lately where
I just barely manage a post a week about what the band is
doing.

My life is in a state where it needs some rearranging, so part
of what I’m going to do is write a post a day about what I’m
interested in then. This might reveal what I’m most interested in
these days, and should be putting more or less energy into.

I don’t promise to keep this up for a whole year, but I’m
calling this set of posts circa63, because I’m starting in August
and my 63rd birthday will be next February.

I may be able to fill in some of the things I should have been
posting about, like BEMF
13
, which I would have written a lot more about if I hadn’t
had the flu just before and my mother hadn’t died just after, and
the death of my mother. I’ll also get you caught up on some
things like the chair
seat covers
I’ve been knitting, and how I’m cooking from the
farm share these days.

Update on the site hacking

It turned out to be the config file that was being trashed.
This is a major hole in wordpress security, because it never gets
changed in an update.

There turned out to be two problems — the one that almost
certainly led to the hack was that it was world-readable, which
shouldn’t have happened, and if it did, an update should have
fixed it.

Googling about the problem also led to reading about the secret
keys
which should be included in your config file, but weren’t
in mine because I’ve been automatically upgrading since before
that feature was implemented.

Both of these problems seem to me to be design flaws in the
wordpress system. I am investigating Drupal as an alternative, but
it’s unlikely to become the site’s underlying technology for at
least a few months. I’m still interested in hearing about
people’s experiences moving a wordpress site to something else.