Wayback machine: link renderer creates redundant https://web.archive.org/web/.../http://web.archive.org/web/ links

[ghostroute]

Wow, so it's quite hard to find how to report a bug against the wayback machine. (My duckduckgo-fu might not be strong enough to get around WBM's success.) I hope this is the (an) appropriate place.

** Problem **

I archived today a ycombinator post, and read it through WBM:
https://web.archive.org/web/20220903091448/https://news.ycombinator.com/item?id=27553274

One of the comments (the fourth one) itself contains a WBM link. It is rendered visually correctly, but the link points to
https://web.archive.org/web/20220903091448/http://web.archive.org/web/20150301234243/blog.ronnyegner-consulting.de/2014/12/10/parity-based-redundancy-raid56triple-parity-and-beyond-on-btrfs-and-mdadm-dec-2014/
(notice the redundancy).

Going to this link I get "The Wayback Machine has not archived that URL. This page is not available on the web because of server error".

Expectation

I assume it never makes sense to redundantly archive the WBM itself. Whatever component modifies the links should refrain from doing so when the URL starts with "https://web.archive.org/web/".

Additionally, a nice improvement would be if the page that displays whether there is an archived version available would give a better explaination when called with such a redundant URL. (Feel free to split this part into a separate component and CC me.)

Stakeholders

If this is not the correct place to report this bug, please tell me where is - and keep me informed whether you forwarded the report or I should do so myself.

Thank you for keeping archive.org awesome !