Good idea, by why not both (i.e. link to a webpage, and to the Archive)?
Linking to Archive only makes Archive a single point of failure.
Linking to Archive only makes Archive a single point of failure.
Check out [this link](https://...) ([archived](https://...))
This can also help in the event of a "hug of death"
<p>
<a
data-archive-date="2020-09-01T22:11:02.287871+00:00"
data-archive-url="https://web.archive.org/web/20200901221101/https://reubenwu.com/projects/25/aeroglyphs"
href="https://reubenwu.com/projects/25/aeroglyphs"
>
Aeroglyphs
</a>
<span class="archive">
[<a href="https://web.archive.org/web/20200901221101/https://reubenwu.com/projects/25/aeroglyphs">archived</a>]
</span>
is an ongoing series of photos of nature with superimposed geometrical shapes drawn by drones.
</p>1. Recognize that it's an Archive.org URL
2. Understand that the link references an archived page whose URL is "clearly" referenced as a parameter
3. Edit the URL (especially pleasant on a cell phone) correctly and try loading that
If you expect the user to be able to go through all this trouble if the Archive is down, you can also expect them to look up the page on the Archive if the link does not load.
But better yet, one shouldn't expect either.
Alternatively, this is a good thing for a user agent to handles natively, or through a plugin.