redirect?

[bumblefudge]

An idea i've been kicking around is that instead of uploading TWO docs at each rotation (/{hash}/did.json AND overwriting /did.json) maybe did.json could just be a symlink or nginx/apache redirect to the current /{hash/ subdirectory? Would that work or do redirects open some can of worms I wasn't thinking about? It would also solve the problem of always being provided the hash of the current signed did doc (because you could extract it from the URL you were redirected to), when used in "legacy mode"

[bumblefudge]

oh speaking of redundant steps and legacy mode, should there be an option step where you put the unsigned did doc at /.well-known/ explicitly called out in the algo? i feel like being explicit reduces ambiguity about what we mean by "legacy mode". one could also mention ?versionTime= and ?versionId= dynamic server handling for the ./well-known path in the historical query section as an option extension of the optional legacy-mode, but that feels like overkill even to me.