Yea no problem, and thanks for caring a lot about it :) appreciate it

It’s a pretty minor thing in the case of your post since, as you said, people can access the link easily after. That’s how I got the link I commented.

The format I prefer seeing is

• Link: Original article link
• Body: whatever content you want to include + archive link

The main advantage is that a lot of apps will use the link to generate a preview image, and sometimes put the base domain. When the archive link is used, there is no preview image and the base domain is the archive site, offering much less information.

So if someone wanted to spread articles from a bad site, people wouldn’t see that it’s from the bad site until they clicked and opened the post (which not everyone does). You could also put a title saying it’s from a news site (ex. Reuters), but actually put something awful in the actual link. Without a preview, people won’t be able to skip it. Also if you know you don’t like a particular site, it’s harder to block it if it’s hidden behind an archive link.

It’s basically all the same issues with the URL shorteners, which is why shortener domains are blocked in a lot of places.

As for the broken site, it is on my end but it’s likely affecting other people with a similar setup. I get this message whereas the actual article loads fine.

Sorry, ReplayWeb.page won’t work in this browser as Service Workers are not supported. Please try a different browser. (Service Workers are disabled in Firefox in Private Mode. If Using Private Mode in Firefox, try regular mode)

This is less important though because I know sometimes the opposite happens, where the archive link works but the actual site doesn’t. The bigger benefit is the point above