In spite of big box retailers’ marketing campaigns, LED lights are still an expensive niche product for homeowners. It’s not surprising, then, that home and design magazines feature them prominently.
Read the rest in my blog post at All LED Lighting, In the Glossies: Gracious Living With LEDs
blogging
Blitzed by @FeedBlitz
Some of you may have seen a scary message when you clicked on a link to my blog post this morning. The service that handles distribution of my blog, FeedBlitz, had a bit of a meltdown this morning. They’ve explained the error in an email and on their blog. In part,
This morning, shortly before 8am US Eastern, one of our databases became overloaded and, to use a technical term, crapped out.
Our monitoring apps told us of the situation, we quickly jumped on the apparent problem, and we thought we were done … but there was more to the issue than at first appeared.
One of our downstream web servers that handled tracking became horribly overloaded as a consequence of its being unable to reach that specific database. That in turn caused a failsafe in FeedBlitz to kick in, which had the nasty and unintended consequence of putting up a scary malware message.
There was no risk to your computer or with anything on www.roasterboy.com. I’m sorry for this false alarm. FeedBlitz responded quickly and correctly, getting the servers back online and communicating pretty well.

Why is Amazon a Mac hater?
Amazon offers a publishing service that delivers blog content to Kindles and kindred e-readers. The subscription costs $.99/month, one-third of which goes to Amazon.
I set up an account and will make this stream o’ bits available through the Kindle channel. (If anyone subscribes, I will donate my proceeds to charity. I’m interested in the publishing process, not in making money.)
One annoying hitch, however, is that, when I go to the publisher’s page to log in to my account, I’m greeted with this warning.
Internet Explorer isn’t available and you really have to dig to find Firefox versions older than the current (17.0) release.
It turns out that the message is benign. Safari and Chrome, the two browsers that I have installed on my Mac, work ok.