Suggested enhancements

Note: this page is quite old. Most feature requests and bugs are tracked as GitHub issues on our GitHub site. Feel free to file one for any bug or feature request.

This page is to track major features that have been suggested for future development:

• Chrome support: A very common request. Currently, google chrome does not support the APIs we would need to implement Perspectives as we do in Firefox. We are currently working on a proof-of-concept for chrome, see: https://github.com/disrani/Perspectives-chrome. If you have experience with Chrome development, please contact us.

• Ability to override certificate errors for sites referenced in embedded content (e.g., when a page for www.google.com references images.google.com). See issue filed here

• Consider caching more on the client side, or even pre-emptively pushing data to the clients. This would have privacy benefits for clients, prevent adversaries from dropping requests, get faster lookups, survive notary failures, etc.

• Browser-agnostic HTTPS proxy to run on a browser users's machine. This proxy can monitor the sites being visited and the certificates being returned and query notaries for consistency. If the certificate is inconsistent, the notary can return an error message instead of the page. Conceivably, the proxy could even play man-in-the-middle for all SSL traffic, so if the browser trusted a the certificate used the proxy, we could have the browser trust even self-signed certs if they were validated by Perspectives. The user could configure perspectives preferences and view notary results using a special set of "fake URLs" that are answered by the proxy itself, for example: http://perspectives-proxy/results . A few people are starting to work on this, let us know if you want to help.