If your user has to care about the file/database distinction, your abstractions have leaked all over the floor.
Did you read the article?
> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that".
Though I would feel a lot worse if I started commenting on the rules without having read them.
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?
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.