@fastfinge Do you happen to know if either you, or the Mastodon alternative software you're using, is doing something special with links? They show up as incomplete URLs in TweeseCake with no scheme (i.e. missing "https://"), and hence can't be directly opened. This is almost certainly a TweeseCake issue too, I'm just curious.
@jscholes@fastfinge This link works fine with Toot! Interesting. Your client seems to have lots of issues. No I mean the whole app but well. They have to consider that re-write faster. LOL.
@jscholes@fastfinge Or, now that I have looked at the software, it's iceshrimp and that is definitely not supported by tweesecake. Try using TWBlue and see if you have similar issues. That one works with Go to social pretty well.
@jscholes For clients that support it, we provide formatted text, so the link is actually not just a url. Tweesecake is showing you the formatted version of the post, even though it only supports plain text.
@fastfinge@jscholes Curious minds must ask if it's markdown formatting or something else? Also, what kind of programming is showing the formatted text but not supporting it? This has gotten an existential programming crisis...
@jscholes It might be possible to fix this by re-ordering the fields in the JSON object. I suspect what’s happening here is that Tweesecake is assuming the JSON has a guaranteed order, when it does not. Mastodon just happens to order it one way, and Iceshrimp orders the fields differently.
