For example:
`import { assertEquals } from "jsr:@std/assert@1";`
could be:
`import { assertEquals } from "jsr.io/std@1/assert";`
With this deno could assume https, as well as follow configs/redirects to get the correct import, then lock those correct paths using import maps (the logistics of this would need hashing out, but it doesn't seem impossible considering they do it with the "special" `jsr:` specifier).
It seems like this would maintain the same pros while avoiding the "special" specifier hard coding that exists now (seems to only be for npm: and jsr: right now; no github: for example).
[0]: https://github.com/denoland/deno/blob/8c2f1f5a55a2a9bb9e04c1...