Chrome appears to have some fairly serious bugs that can lead to deleted bookmarks. I tried deleting a single bookmark in the bookmark manager, and it ended up deleting an entire folder. Fortunately, there is a Bookmarks.bak available until the next time you quit chrome. This wouldn’t have been such a big problem if I hadn’t already been fighting bugs with the Xmarks bookmark syncing plugin for Chrome. I have now turned on Chrome’s built-in bookmark syncing, but I still use Firefox quite a bit, so I wish Xmarks and Chrome weren’t so buggy. This is why I normally avoid beta software like the plague.

http://www.google.com/support/forum/p/Chrome/thread?tid=56d0b36c2e503bd6&hl=en

http://www.osnews.com/story/22872/Linux_Not_Fully_Prepared_for_4096-Byte_Sector_Hard_Drives

This is a like a CSI episode on flash memory.

http://www.bunniestudios.com/blog/?p=918

Currently, PostgreSQL replicates a database WAL (change log) files to the slave databases, which made it more difficult to get slave databases to have less than a minute of lag. This wasn’t a big deal, since before 9.0, which is in development, you couldn’t query the slave databases until you failover, which stops replication, and that’s a rare event. With streaming replication, it will be possible for the slave databases to be as little as one second out of date, which makes them much more useful for offloading read-only queries from the master database.

http://www.depesz.com/index.php/2010/02/01/waiting-for-9-0-streaming-replication/