We’ve been lucky this summer and had relatively mild weather. However, this week our luck has run out, as we contemplate heat index readings over 115 degrees (46 celsius).
Stay cool.
Categories
Beijing on a smoggy day
Recovered from the Wayback Machine.
I have been following James Fallows’ coverage of the Olympics with interest, specifically because he has been focused on the air pollution that plagues Beijing.
It is unfathomable that a city would put its people at risk by having air quality so bad that it has to take such drastic steps as eliminate 90% of cars from the road and close most of its factories, in an attempt to clear the air for the games. By all accounts, the effort is not succeeding, and rightfully so. If concern about its people does not move the Chinese government, perhaps embarrassment in front of the world will do the trick.
Fallows had written once that he hopes the Beijing games succeed, because if they fail, foreigners in China will be blamed and their lives made miserable. With all due respect to Mr. Fallows, and with empathy to those who are in China for their jobs, I hope opening day of the Olympics dawns a brown, moggy mess.
Thanks to a link provided by Ryan in comments, an excellent review about a new movie, Dark Matter, and its indirect association to our relationship with China, and the importance of the Beijing games being successful. It gave me food for thought, but hasn’t necessarily convinced me to change my opinion. We’re facing a desperate situation, environmentally, and China’s environmental policy hurts not only the Chinese people, but the rest of us, as well. I find that difficult to overlook.
Categories
Planning your own EOL
This week I’m updating my will, which hasn’t been updated since I was married (I’m now divorced). Updating one’s will is never a fun task, but it is essential if you don’t want to leave a mess behind after you die. More importantly, you may not always want everything you own go to Nearest Next of Kin, or the courts, if you die intestate (without a will).
In my case, a will is simple since I don’t own a house or business, and don’t have kids. I’m including in my will my bank account number, and my car insurance policy account information, in addition to the online accounts I’ve set up for both. I do have royalty payments, but it’s a simple matter of just specifying who the royalties go to. Of course, I also have to leave instructions about what royalties I am expecting and who to contact to ensure they go to the right person.
Then there’s this web site, and therein lies a modern challenge when planning one’s own EOL (end of life): what do we do about our connected lives?
I currently have automatic payments set up to pay for phone and internet, as well as my web site. To ensure that these are managed property, I’ve included instructions and access information for both.
I’ve provided a list of people and their email addresses to be notified if I die, so I won’t suddenly disappear without a trace. However, I have no interest in my web site lingering much beyond my death, as some form of white cross along a virtual rather than real highway. I realize that my web site going away will leave holes where previous documents used to be, but whoever decided that the web must remain static and 404 free really didn’t think through the issues in their Utopian view of the internet.
As for my writing or pictures, whatever I do have online is free for the taking after my death. Oh, the copyright will still be there, but my “heirs” will not be going after anyone. I haven’t decided yet, but I may ask that my online material be turned over into the public domain after I die. I’ll have to explore the ramifications of this issue in more depth, as there are some pieces that some people may want.
The domains I own will, themselves, be allowed to expire unless my heirs decide they want to keep or sell them, early. I will include information about how to access my registrar account, as well as my web hosting account.
Speaking of domains, currently I have several email addresses dependent on burningbird.net. I’ve already started using my Gmail account as an intermediary for sign up accounts, and I have to start doing the same with other email addresses I maintain. My email server will be gone once my web site is gone, and I don’t want others to suddenly lose email access because I’m no longer around to maintain the email accounts.
My Kindle is set up under my account at Amazon, and I’m not sure how one goes about “leaving” my Kindle books to another. I would assume that since these are property, and since the actual physical device goes to someone, the books themselves do, also. I’ll have to ask Amazon what its recommendation is. My Netflix account must also be transferred, which means transferring the Netflix Roku box to another account.
Other than my web site and email addresses, as well as online accounts with service providers, I don’t have any investment in any other online social services that I have to worry about closing.
Online accounts are not the only issue, though. I’m the tech in my household, and the only one with knowledge of how all the pieces are fit together. This week I’m spending time writing out detailed instructions of how all the components of my various systems fit together: from how to access movies on my AppleTV (including which computer is synced to my AppleTV, and what my iTunes account information is); to how to access movies, Hulu, or other online account from both my Mac and my Dell laptop.
These latter activities may seem frivolous when compared to the event leading to the need for such documents, but it seems a shame to do a really nice job with a home intranet, only to have it fall apart if I’m not longer around. Plus if I’m not dead, but only incapacitated for a time, or even on a long trip, it would be pity if my roommate couldn’t access my rather spiffy video setup.
To summarize the tasks:
- Do the usual: create will, assign executor, provide detailed bank account information, as well as information about car insurance, and other insurance policies. Make sure to note all sources of income, even sporadic ones. (Getting money from selling ads, or being an Amazon associate? Note these.)
- Provide a contact list of who to contact if you’re dead or may be dying.
- Sign up for and use a centralized email account for any accounts. Have the account forward email to your hosted email account.
- Leave instructions about how to access your web hosting account, and what do with your online material if you die.
- Leave detailed instructions for all other online accounts, including your domain registrar, Amazon, Paypal, iTunes, FaceBook, Twitter, and so on.
- Leave detailed instructions to access all your accounts that are setup with automatic payments. These will need to be transferred or canceled.
- Provide account information for all computers, too, unless you want the computers wiped clean. Don’t forget your iPhone or other cellphone or small devices.
- If you participate in some committee, such as a W3C working group, or provide open source software, such as Drupal modules, Firefox patches, then provide information about who to contact and how to provide access to any work in progress, or ensure that someone in authority knows that a module or other work is now available for someone else to support, if they wish. The same goes for any conference or other event where you’ve made commitments. Notice of death may be sufficient.
- If you’re responsible for the internet or intranet connectivity in your home, (or church, or other organization outside of work) document your connections and equipment, and make sure whoever needs access to this information has these documents, and understands these documents. I am assuming you’re already doing this for your job.
- To ensure you’ve accounted for everything, keep a diary, and every time you access a new online account, work on a new project, make an adjustment to a new device, make a new work or event commitment, jot it down and make sure the diary is accessible to whomever is your executor.
It is actually quite a lot of work to prepare for one’s own end in in this era of subscribed services and internet accounts— not to mention long distance relationships, and plethora of connected devices. I think, though, it’s important to do so if we don’t want to leave behind a tangled mess.
We should do this type of planning no matter how old or fit we are— there’s nothing morbid about planning for one’s death, and age is no defense. After all, there could be a beer truck with our name on it, just around the corner.
Categories
Shiretoko: First Looks
I downloaded the first alpha of Shiretoko, or Firefox 3.1, and I’m delighted to see the text-shadow I have attached to my site name showing up in a Firefox browser.
Not just text-shadow, Mozilla has also added JavaScript query selectors to this release, which means that we can query for all elements of a given class name, such as:
var list = document.querySelectorAll(".elements");
A behavior that we also had with the older, supported, document.getElementsByClassName. However, we couldn’t do the following with getElementsByClassName:
var first = document.querySelectorAll("div > p:first-child");
for (var i = 0; i < first.length; i++) {
first[i].style.backgroundColor="#f00";
}
This code snippet accesses the paragraphs that are directly the first child of any div element, using the CSS selector syntax, and sets the background of each returned element to red. You can see it in action with this simple example containing three div elements, each with three paragraphs, the first of which now has a red background. Well, you can see it with browsers that support querySelectorAll, which are Safari/Webkit, IE8, and now Firefox 3.1a. Opera has also committed to the support of querySelectorAll (as well as rgba, we hope).
Of course, I can do something like this with JavaScript by getting all div elements, and then all paragraphs of all div elements, and then accessing the first of the returned set, but how much simpler, and how my more robust will this process be if this type of functionality is built directly into the browser. Especially since my example is quite simple, but other queries on CSS selectors could be quite complex.
Firefox 3.1a also has support for border images, which means no more nested div elements to achieve specialized borders, which is what’s used in the design of this site. However, support for this CSS3 attribute is limited to Firefox 3.1a and Safari; until support for the option reaches three of my four target browsers, I won’t use it for my site designs.
(I felt comfortable using the text-shadow when only Opera and Safari supported the CSS attribute, because it provides such a nice effect, which degrades beautifully if the attribute isn’t supported.)
Firefox 3.1a also supports the HTML5 Canvas Text API, but I haven’t had a chance to play with the new capability, yet. I had rather hoped that the Mozilla team would add a little SMILe to the browser, but I guess it’s not to be with this browser release. Perhaps our man on the SVG street, Jeff Schiller, can update us on a SMIL timeline for the browser.
Oh, and look: anyone can try the browser and report a bug.
Categories
Last of the book and attack of the women
I put the finishing touches to the draft for my current book, and now it begins the technical review process. I don’t want to say it’s my last book, but there is no other on the horizon, as I return to the world of software development and consulting.
First, though, I need to spend time upgrading my own skills. When you write books, you have to let so many new and interesting technologies slide by because you don’t have time to stop, and play. You also end up coding in small pieces, because you’re focusing primarily on book samples, with little time for larger applications. Or that playing, I just mentioned.
I want to spend more time with Drupal, because I’ve only scratched the surface of this application. I am extremely pleased, nay tickled to see Angela Byron from Lullabot win an award for Best Contributor at OSCON for her work with Drupal—affirming that my move to this software was the best move for me. In fact, in sounds like women made significant inroads in the open source community at OSCON this year, aided, in part, I think, because of software communities, such as Drupal, which are decidedly woman friendly environments.
In particular Emma Jane Hogbin’s Form an Orderly Queue, Ladies presentation at OSCON provides details of a dastardly plot to infiltrate women into the ranks of the tech through open source. I love evil plotters, like Dr. Horrible, and evil plots, like women invading open source through innocent seeming applications like Drupal. Drupal and Dojo.
Bwa-ha-ha.