[cap-talk] Google Chrome - web browser with sandboxed rendering

[James A. Donald]

Ben Laurie wrote:
 > The problem with this design, though, is that it
 > relies on the user to know that "aha, if an app wants
 > to use the POP3 prototocol, then I should insist that
 > it uses the trusted POP3 component". Tying this to
 > port 110 is obviously not a great idea, so we're back
 > to UI that is going to confound most users, surely?

Obviously, if my solitaire app wants to use the POP3
protocol, something is up.

There should be a finite, and not very large number of
install patterns with user intelligible names - the user
can create more install patterns, but only if he likes
hacking.  If something is not installed as an email
client, it should not be able to do POP3.  If the
solitaire program wants to send email, it should just
fail.