2025-11-26T01:30:24Z
Create a configurable "pecking order" of URI schemes so the precedence is unambiguous.
How do we resolve RFC6920 content addresses to their HTTP(S) counterparts?
Overhaul the resolver so that it has pluggable transformations between durable identifiers and routable addresses.
What happens if a resource has more than one durable identifier?