An additional problem - the site https://lemmyverse.link/ is available only partially (requires VPN to work).
So my new idea is to deployhttps://github.com/RikudouSage/lemmyverse.linkinto my website locally, and give 2 links - the relative (via local redirector) and the direct one (as a fallback).
the relative link on forein server will became broken, until they also install such redirector into the same path.
After that the link will always lead to local server and redirect to preferred server of user.
«Your original url is right there in the path if it were to go down»
But how it's supposed to help one, to see the original URL?
It will help only if the content is archived in some way.
If remote lemmy server will go down. Then content will became unavailable, even If I install a local copy of that redirecting engine.
localhost(2026-07-19|14:57:51) ~/rust$ rustup update stable info: syncing channel updates for stable-x86_64-unknown-linux-gnu info: latest update on 2026-07-16 for version 1.97.1 (8bab26f4f 2026-07-14) info: removing previous version of component cargo info: removing previous version of component clippy info: removing previous version of component rust-docs info: removing previous version of component rust-std info: removing previous version of component rustc info: removing previous version of component rustfmt info: downloading 6 components cargo installed 10.63 MiB clippy installed 4.71 MiB rust-docs installed 22.73 MiB rust-std installed 28.71 MiB rustc installed 77.30 MiB rustfmt installed 2.06 MiB stable-x86_64-unknown-linux-gnu updated - rustc 1.97.1 (8bab26f4f 2026-07-14) (from rustc 1.96.0 (ac68faa20 2026-05-25)) info: checking for self-update (current version: 1.29.0) localhost(2026-07-19|15:01:20) ~/rust$I think that it should do backups first and remove only in the end. Or do parallel installs.