Educating the user is not the solution. And even having a pop up saying that an update is available is too much. One way or another the user will find a way to screw it up. Security should not depend on any action from the user perspective. This would presume that the user at the keyboard is actually a friendly. Educating the programmer to develop transparent security needs to be a first step.
Actually a filesystem is not that bad of an idea. Using the Coda filesystem to bring the file I/O calls to user space, you would not need much more development time to drive the calls to Gmail, especially if there is a webservice interface.
Slashdot Mirror
Educating the user is not the solution. And even having a pop up saying that an update is available is too much. One way or another the user will find a way to screw it up. Security should not depend on any action from the user perspective. This would presume that the user at the keyboard is actually a friendly. Educating the programmer to develop transparent security needs to be a first step.
Actually a filesystem is not that bad of an idea. Using the Coda filesystem to bring the file I/O calls to user space, you would not need much more development time to drive the calls to Gmail, especially if there is a webservice interface.