>but what's wrong with expecting people to know a little?
The issue here is that you're training users to rely on internal details.
Once users have to rely on internal details, you are stuck with maintaining these forever or face a constant stream of backlash.
this is about a distinction between entries in a database (files) and the database itself (the filesystem is a DB).
but what's wrong with expecting people to know a little? would you argue that if the user sees the whole URL in the browser that the abstractions are leaking?