@catodon@catodon.rocks @panos@catodon.rocks I just noticed that the link that's supposed to be the url of the original post is instead federated as the link from the post. Can't imagine this being intentional

Yeah, actually it's on purpose, with this known downside. For link posts in our forums, we put the link in the post's url field, the same way Lemmy does. We did this as a compromise, because otherwise NodeBB wouldn't show the link. The side effect is that Mastodon-style apps treat url as the post's own address. "Open original page" then opens the link instead of the post on the Catodon server.

@julian@activitypub.space - hello! I have not checked if NodeBB has changed this since we implemented federated forums. if we send url as a list, with the post's own address first and the link second, would NodeBB still show the link? We also send the link as a Link attachment. Ideally, we would like to keep NodeBB working and fix Mastodon too.

@panos@catodon.rocks @catodon-talks@catodon.rocks @julian@activitypub.space
wait, that can't be right. Lemmy does not do that, it doesn't have the top-level url in post AP object at all, neither I ever had this issue with Lemmy linkposts and I can't reproduce it now, it's original post url resolves correctly, even on Mastodon.
And NodeBB source at least gives the impression that it can pull the href from attachments?

@lnkr@staging3.plamenu.com @panos@catodon.rocks no this doesn't seem right.

NodeBB does not handle url that way, it always represents the user friendly URL that a browser can access.

The specific case you're referring to is a threadiverse post with a link target. In that case the shape is attachment with type Link. NodeBB checks for that and appends it to the post body.