Please keep in mind that not everyone on other Fediverse instances have access to the one you're linking to. The same article can be accessed publically by any visitor at this URL:
You did nothing wrong; I tried to visit the link you posted initially (which is on the sopuli.xyz instance; I am on the meow.social instance) and was instructed that I needed to log in to that instance to access the thread wherein the article was hotlinked out of.
For whatever reason the second time I did so I was able to enter the thread you linked to and could visit the Trekmovie site it linked out to. I don't believe there was remotely any malfeasance on your part, only that on my initial attempt to use the link I couldn't access it.
Weird, I didn’t link to my instance or a thread on my instance at all. From what I can see I posted the exact same link that you did - direct to trekmovie.com. Not sure what is going on.
@Klanky I believe you, and I think my initial and firmer tone was perhaps uncalled for; I apologize for that.
I should mention that you are also posting from the 'sopuli.xyz' instance; I am not familiar with the bulk of cross-instance posting mechanics but it may simply be an unusual, if unfortunate abstraction of behaviour in how posting works and links behave on the original post's instance and Fediverse instances other than that.
No problem! I’m more curious what is going on. I did create the post while viewing the Star Trek instance from my sopuli.xyz instance. Like you said, it might be a quirk of the Fediverse.
They linked directly to the post on the Lemmy side, so I’m guessing it’s an issue with how Mastodon handles Lemmy posts. I’m on a different Lemmy instance and I can see the direct link just fine.