Some issues came up in the new datasette-hashed-urls plugin relating to the way it renames databases on startup to achieve unique URLs that depend on the database SHA-256 content:

• Renaming the database names makes crossdb queries very brittle datasette-hashed-urls#10
• On database page, have the database name without the -HASH suffix datasette-hashed-urls#9
• Restore behavior where the link text is the unhashed db names datasette-hashed-urls#8

All three of these could be addressed by making the "path" concept for a database (the /foo bit where it is served) work independently of the database's name, which would be used for default display and also as the alias when configuring cross-database aliases.