I expected some special syntax like post:id!community@domain
Or ap_id?post/15@xn--e1aghfa.xn--e1aqbccjfc.xn--p1acf
Here ap_id is the name of part of URI, which maps to
https://lemmy.ml/post/ap_id
and performs all the magic, which lemmyverse.link does
Or https://lemmy.ml/post/49064481?15@xn--e1aghfa.xn--e1aqbccjfc.xn--p1acf
if developers will integrate it into lemmy itself
?=post/15@xn--e1aghfa.xn--e1aqbccjfc.xn--p1acf - any ap_id
?!community@xn--e1aghfa.xn--e1aqbccjfc.xn--p1acf - any community
?usernick@xn--e1aghfa.xn--e1aqbccjfc.xn--p1acf - any user
but the last two options are not necessary



in another software it’s possible to use:
p?ap_id@server
c?conf@server
u?user@server
where this local links will be added to URI ending with trailing
/i.e. https://engine.tld/application/objtype/NNNNNID/
will be completed with
https://localserver.tld/applicationname/objtype/NNNNNID/p?ap_id@remoteserver.tld
https://localserver.tld/applicationname/objtype/NNNNNID/c?conf@remoteserver.tld
https://localserver.tld/applicationname/objtype/NNNNNID/u?user@remoteserver.tld
This way the local links will allow to setup redirects to any type of objects.
(and without the special syntax and special parsing)