The first is a history API that allows developers to modify the user's browsing history. When the API is complete, develops will be able to replace the user's history with their own. The second API is more of a processes API. This API gives third party developers access to Chrome's process model, such as information on the CPU usage for each tab.
To me this sounds like it could be a security risk to home users but I know that Google does monitor extensions that attempt to access files from your computer. These APIs are available now in Google's Dev Channel and they encourage people to play with them a bit and then give some feedback.
Post can be found here at The Chromium Blog
interesting, both those APIs sound like security concerns to me.
ReplyDelete