thoughts on chrome
Using a separate process for each web page and each component has been something I've always wanted a web browser to do. It's so conceptually clean and has such nice properties, and processes are so cheap in linux. Hats off to the people who made that a reality.
On the other hand, I'm guessing that chrome's guts will be tied into the google backend services so tightly that you can't really tell where the one stops and the other begins. Since I'm not interested in being a sharecropper, and would prefer to see people empowered with services they control, I have worries.
It's easy to forget how much of the modern browser's er ... chrome ... is
based on web services that could change, go away, or be DNS hijacked at any
time. I'd like to see a web proxy that takes all traffic to *.google.com
and rot-13's it, to demonstrate how many things rely on this one company.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!