Posts Tagged ‘Twitter’

Weekly Reading… and We’re Off!

Thursday, June 26th, 2008

We’re coming to the end of our last full day in London, and it’s been action-packed right up until the end. Evan’s been busy finishing up Hellboy II — go see it in the U.S. July 11 and in the UK August 20 (or July 13 at Somerset House) — and I’ve been busy redesigning the Write-Communications site (with help from a great Revolution theme and lots of Wordpress plugins), doing work for Workology and still trying to get a bit of writing done.

The weekly list:

On our trip we should be making occasional updates to Twitter (me/Evan), Facebook, this blog and Evan’s photo site, so stay tuned. Now off to do some more packing — we head to Egypt tomorrow!

Technical Problems Are No Fun

Friday, November 9th, 2007

This is more a little rant about problems I had yesterday than what’s going on today, but I don’t know if anything has really been resolved, especially with my biggest issue: My keyboard keeps randomly freezing. The problem doesn’t seem to be tied to any specific program I’m running, and the more I research it, the more it seems to be an issue with Leopard, which I installed last week. I’m hoping for a fix soon because it’s really quite a pain to have the whole keyboard freeze up and not know when it’ll return. At least the touch pad still works when the keyboard is out.

I was also having some issues with Google Reader yesterday. I was trying to clean up some feeds I don’t need anymore, but it kept giving me errors midway through the cleanup process. I was so annoyed, I even downloaded a different feed reader, Sage, but found it lacked some of the GR functions I really like. So today it was back to GR and thankfully my cleanup worked. Back to business as usual, though even with my big cleanup I still have 1000+ unread items. Thank goodness for the “mark all as read” button.

And on top of all this, I also had some Twitter issues. I made a few posts that just never showed up. My internet was working just fine, so I don’t know what the problem was. Seems to be fine today, though.