When I found Magic Prefs which is a Magic Mouse preference and configuration utility for OSX. Without this program, the mouse only comes with 2 touch sensitive gestures. I have no idea why Apple wouldn’t want to capitalize on more features with this fully functional multi touch surface. But the good news is, with Magic Prefs you can configure a very broad range of clicks, touches, swipes, and pinches to actions with your mouse making it a true multi touch surface.
I have had my Magic Mouse for a couple weeks now and my biggest pet peeve with is was the physical click. It’s not like other mice where its easy to press down on left and right click, the Magic Mouse is very noticeably harder and you really tend to notice it after couple hours of use. With each click I seem to be more and more conscious of my physical ability to left and right click. Lucky for me with Magic Prefs you can configure tap left and right tap clicks just like the multi-touch pad on the Macbook Pro. It’s a very little and simple feature, but has made me a much happier Magic Mouse user.
I highly suggest checking out Magic Prefs if you own a Magic Mouse.

Only about an hour ago it was announced that the droid has been rooted.
Alldroid.org post with download + instructions etc.
Authors Post:
md5sum of initial exploit zip: 94a0c30ea9104c2776d042e760bfd716
URL: http://rapidshare.com/files/318204448/d … t.zip.html (Down now?)
URL2: http://www.4shared.com/file/168496608/8 … -root.html (thanks, blunden)
URL3: http://www.mediafire.com/?ydaqjmditjh (thanks, blunden)
URL4: http://www.multiupload.com/XYPZLK4K22
Also attached in a thread post.
The exploit provides a /system/bin/su from AOSP (that is, you can only use it from adb shell).
Other payloads can be arranged, but I’m too lazy to make them myself.
Provide a decent payload and I will turn it in to an update.zip that the Droid will apply.
Restrictions: The payload zip must be <63k
I can add files already in the official update to it (update-binary).
Some possible install instructions (unconfirmed):
md5sum of the boot partition:
3e49d99b320cf5c20bedf09343c1155c /dev/mtd/mtd2
HOWTO
Download the zip file (see mirrors in posts below)
Rename to “update.zip” and copy to the sdcard
Power off the DROID and power back on while holding the X key
When you see a “/!\” symbol, press both vol+ and camera
Use the onscreen menu to install update.zip
Once installed you will be able to run “su” from your adb shell.
I recently put a completely new rig together freaturing the new Intel i7 processor and let me tell you, this thing is a beast. Greatest x86 multitasking CPU out there. I went with the i7 920 @ 2.66ghz. This is a quad-core chip with 2 hardware threads on each core so a total of 8 cpus.
Full specs:
After purchasing and finally building and configuring my new system, I was looking through google trying to find more information on the i7 I just purchased and it came to my attention that the exact chip I bought is very over-clockable.
The guys over at bit-tech.net were able to push their 920 up to 4ghz and they got some pretty good benchmark results.
Tom’s Hardware was able to oc their chip to 3.8, but thats nothing compared to one of their users who got their i7 965 to 5ghz!
So after seeing how easy it was to overclock this thing and that I had the same hardware as most of these overclockers, I decided to give it a try for myself.
First I ran a couple benchmarks with stock settings and this is what I got.
Then I was able to get my CPU up to 3.2ghz. I have stock cooling and some crap ram so I am kind of afraid to push any farther. Plus I am plenty happy at 3.2 anyways.
These are the voltage and clocks I set:
There were a few CPU related features I turned off/on based on what I saw in the bit-tech article.
I’m sure I could of gone to a higher clock speed and maybe I will once I get better cooling equipment and better ram. It seems that the DRAM clock and the over all CPU base clock are relational and I can only set the DRAM clock in certain 200mhz steps and those steps based on what the CPU base clock is at so my DRAM clock options are usually too high, or too low. Since my ram seems to crap out at around 1500mhz, the best thing for me to do is to try to take the CPU clock higher until I can hit a theoretical sweet spot clock speed (though it would still be better to have bought the better ram in the first place).