While testing the behavior of hyperdrive-open (and hyperdrive-open-url) when called on URLs to non-existent files, I noticed that, when the URL points to a writable hyperdrive (i.e. one's own hyperdrive), rather than showing a message about the URL pointing to a non-existent file, a buffer is opened for the file (i.e. like calling find-file on a non-existent filename). This feels slightly unintuitive, as it seems like hyperdrive-open-url ought to behave more like a Web browser, in that it should signal an error if the URL points to a non-existent file; i.e. it seems to me that hyperdrive-find-file and hyperdrive-open-url ought to behave differently when trying to open non-existent files. To put it another way, this behavior makes it sometimes feel non-obvious whether a filename actually exists on one's own hyperdrive, as it makes it harder to distinguish the case of opening an existent vs. non-existent filename.