Note by @fastfinge

@Bri @jdking92 @Rosalyn Some can also just post HTML directly. Either way, when you strip the HTML, you get the link text, without the URL. Usually, the link text is the URL without https in front. But it doesn't have to be. GoToSocial, Akoma, Iceshrimp, Pleroma, Sharky, threads, Lemmy, PiFed, and literally anything other than Mastodon allow for text in the post that is a hyperlink, but does not contain the URL as the link text. Even though Mastodon doesn't allow posting like that, though, it can display that type of post. So because of the way FastSM strips HTML, it can only find links posted by another Mastodon server. Every other server type can post links that FastSM users can neither see 'nor interact with. Even Mastodon forks can do this. As someone effected daily by this issue, because it's completely and totally impossible for me to post links that tweesecake or FastSM users can interact with, no matter what I do, this is a huge priority for me. Only supporting logging into a Mastodon server account is one thing, and I get it. But the way FastSM is currently, you only support viewing posts by, and following, users who happen to also be on Mastodon. If you follow an account using literally anything else, links won't work. And it's impossible for a FastSM user to know they've followed an account on an unsupported server type. It's to the point where I avoid posting any links at all, because every single link I post gets multiple replies (sometimes as many as thirty or more) from blind users who do not understand that the client they use is at fault and in complete violation of the standards, not me. I'm one hundred percent following the standards as defined by the W3C and all of the Fediverse Enhancement Proposals. Clients that can't handle formatted links are broken. They need to be fixed. I've had to start just blocking Tweesecake users. I don't want to have to also do that with FastSM users.