I agree. I just spent thirty minutes with a new user dealing with just this issue. He double clicked an existing rev db, using Nautilus. Revelation started, but with a empty db. He added a new password entry, then got confused when saving. I know the feature is a feature (not like Microsoft bug being called a feature).

But it's hard enough to get a 50+ year old person to take security measures at all. Why make it harder?

Perhaps a 'usage counter' method to remind the user to explicitly open the file via filechooser. Say 20 reminders before the beginner method fails. The reminder window could have helpful tips too.

I agree with this proposal - there is a workaround: you can add the database file as a command line option, this allows creating a shortcut (at the desktop or a panel) with the right database included. just edit the shortcut properties to change the command to look like e.g. "revelation /home/jdoe/myWebKeys" for opening the database "myWebKeys" in jdoe's home directory.

+1 on this. This tripped me up, especially because I decided to use a .revelation directory, and dot directories are awkward in the file chooser. This was made worse by the fact that revelation did not remember my new password database the next time I opened it.

I agree on this, too. It save some time when you don't have to look for the .revelation file everytime you open the app.

There is an option to automatically open a database-file when you start Revelation:

1) Go to "Edit" -> "Preferences"

2) Under "General" -> "Files", mark "Open file on startup" and pick the correct file

From now on:

1) Open Revelation from your application menu or panel-/desktop-launcher

2) Type in your password

3) Do whatever you like