1. First, grab the root cert file from the CACert Root Cert page. You should verify that the file is correct and has not been tampered with; md5sums and SHA1 hashes are included, along with the fingerprint signed by the CACert GPG key. I'll leave it as an exercise for the reader as to how authenticity should be verified, but for the moment let's assume we have a good, trusted copy of the CACert Root Certificate (PEM Format) saved as root.crt in your home directory.
2. If you've not already, you should install the NSS tool set - a simple sudo aptitude install libnss3-tools should work nicely. You will be asked for your login password to ensure you have permissions to install software.
3. Install the CACert root key by running certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "CACert Root Certificate" -i root.crt
4. There is no step 4... you can now go to CACert secured web pages and Chrome will correctly verify that the SSL site cert has been signed by the CACert root certificate.

1. If you've not done so above, you'll need to install the NSS tools, using sudo aptitude install libnss3-tools or similar.
2. Next you'll need to get a copy of the certificate. Particularly with embedded devices, the easiest way to do this is by pulling the key directly from the device by pretending you're a web client. Thanks to tgulacsi78 who suggested echo QUIT | openssl s_client -connect hostname:443 | sed -ne '/BEGIN CERT/,/END CERT/p' - replacing hostname with the name of the host. In my case, I might use echo QUIT | openssl s_client -connect eeyore.han.signal2noise.ie:443 | sed -ne '/BEGIN CERT/,/END CERT/p' to get the cert from eeyore, my wireless router.
3. Copy and paste the lines between 'BEGIN CERT' and 'END CERT' into a file and save it as (say) router.crt
4. Now we import the cert in exactly the same way as previously, using a command line something like certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "My router web admin certificate" -i router.crt
5. Note that we have to use the C flag (i.e. mark it as a CA / Certificate Authority) due to a bug in NSS. Note also that you should replace the description after -n with something that means something to you, and the argument after the -i should be the file name and path to the file we created in step 3.
6. Test that everything has worked by using Chrome to access the site secured by the self-signed certificate again and notice that this time no warnings are given.

meebo.com

Meebo is an IM aggregator, allowing you to communicate with all your contacts on different IM networks, including Google Talk, Facebook and many others, from one place. Killer feature is that your conversations follow you around from machine to machine, and iPhone push support works well, allowing you to carry on IM'ing from the iPhone App.

1. Install GlodaQuilla in the usual fashion
2. Restart Thunderbird
3. Disable indexing completely (see above for how to do that)
4. Quit Thunderbird and wait a few moments to make sure it's definitely no longer running
5. Delete the old full-text database taking up space on your hard drive. It's a file called /home/$username/.thunderbird/random.default/global-messages-db.sqlite on my Ubuntu Linux machine. You'll need to find your own global-messages-db.sqlite yourself, but the path above should give you a clue as to where it is.
6. Start Thunderbird and right click on a folder containing mail you do not want indexed. (e.g. my Archive/ folders contain old mail that I don't really need searched or indexed.) Uncheck 'Inherit' and you can now individually enable or disable indexing of the mail folder.
7. Once you have set which folders you do and do not want indexed, remember to re-enable indexing and restart Thunderbird, just to be sure to be sure.
8. Leave your computer for a period of time, if possible, as Thunderbird will need to rebuild indices for those mail folders you left with indexing enabled. This may take some time. Expect performance to be poor during this time. You can track activity by selecting Tools | Activity Manager from the menu.
9. Enjoy a nice, fast, performant full text search of the mails you actually care about searching and indexing.

ip route add default \
   nexthop via dev weight x \
   nexthop via dev weight y
change x and y so that x/y == bandwidth ISP1 / bandwidth ISP2

1. Be up front and open about what information you are trying to gather and why you are trying to gather it. While multiple-choice answers are unlikely to change depending on the reason for the questionnaire, free-form text answers are likely to be quite different. I'll except those doing psychological research from this rule, since they typically have their own reasons for asking certain things in certain ways.
2. Be honest about how long it will take. Give an estimate at the start so people can decide if (a) they want to devote that much time and (b) if they have that much time available in one block now, or should wait until later to start. Estimate on the high side. Ask three friends of yours to take the survey and time them - see how long it takes them to fill it in and use that as a gauge. If it's a multi-page survey, provide a progress bar. Make sure the progress bar is honest and realistic about progress at every page.
3. Use less pages, particularly on web surveys. Remember that ever time I have to click next wastes time as my browser has to download a new page, render it, etc., etc. In particular, stop the foolishness of asking one question per page. If I wanted to click next all day, I'd install Windows software for a living.
4. Don't make questions compulsory. Allow me to progress without answering a question. It might be that I don't have an answer, don't want to give an answer, or that I want to come back to it later.
5. Don't ask for personal details, in particular things like date of birth. If there is a genuine reason you need such information, state why you need it and don't make it compulsory. Any survey I get asking me for date of birth is ignored. If you are building up a statistical model that requires the person's age, ask them that - or ask them their year of birth, or even the month and year. If you need such information, explain why and detail how you are going to protect such personal information from abuse (e.g. By only storing anonymised data, or similar.)
6. Get someone else to check your questions. For preference, get someone who does not intimately understand your research or line of work to check your questions. See if they can understand all your questions, and indeed that their understanding is the same as yours.
7. Make it clear whether you expect one or multiple answers to each question. For online surveys, radio buttons should be used to allow selection of a single option, and check boxes allow selection of multiple options.
8. Do not make free-form text answers compulsory, ever. By all means allow free-form text answers or extra 'any other comments' style questions at the end, but do not make them compulsory. In particular, do not echo one recent survey which asked "What made you pick option X?" after each question - and forced some answer to be given before proceeding. This is a classic example of how to erode any good will the survey respondent feels towards you.
9. Thank the respondents and most importantly, tell them what's going to happen to the information and how it will help you. A poor survey will thank the respondent for answering their questions and leave them wondering what, if anything, will happen next. Consider offering to collect an e-mail address and send them a copy of your research when it's ready for publication. If you're a commercial company, offer to provide an update in a reasonable time frame on the results of the survey and what improvements customers can expect because of it. If the respondent declines to give an e-mail address or contact details, consider giving them a URL where they can find more information about what will happen with the information they've just given you. People like feeling useful - make your survey respondents feel useful!

"Broadband is an always-on Internet connection that gives you high-speed access and downloads for a flat rate monthly charge.
Everything works faster, from downloading emails and files (such as pictures & mp3's) or streaming movies and radio."

• Could be made smaller
• Allowed hiding of things like the tabs and menus and other useless bits
• Retried gets without constantly moaning about things failing. It's the internet - get over it. I don't need an orange triangle to warn me that the twitter API or the internet dropped a packet or two.
• Retried posts more than once - maybe even until they work - instead of logging a meaningless error and losing my post. Something more than an orange triangle would be good to say a POST failed.
• Could track whether I've read tweets or not - and maybe highlight the ones I've not read?
• Could get more than about 20 tweets on startup - maybe make it configurable, or even continue getting historical tweets as long as they are unread by me (up to a configurable max)