Speaking of the principle of least surprise ... @jdp23 is post got auto-boosted by @activitypub but there wasn't anything that indicated to me that was going to happen.

And, from GoToSocial, the topic's subject shows up nicely from Julian, @jdp23's reply lost the topic, but it showed back up in Julian's reply to the (topicless) reply ... Behavior's similar on Sharkey, although the subject doesn't render as nicely (but it's still readable)

With the @thenexusofprivacy account on Glitch, the subjects don't show up at all -- not even in Julian's original post.

@stefan @julian

Replying from a GoToSocial instance ...

I was able to find the parent NodeBB post by searching for https://discussions.thenexus.today/post/52 (the "Copy Permalink" in the NodeBB three-dot menu for it).

However, I *couldn't * find the parent page by searching for https://discussions.thenexus.today/topic/16/can-i-bridge-from-nodebb-to-bluesky/12 - which does work in Mastodon. And that's actually what I looked for first, because that's what comes up from the "Open original page" link when viewing it in the Mastodon web UI. Although Mastodon's "Copy link to post" is .../post/52 , so if I had done that it would have worked, but.

So it looks like at least couple of things going on:

- GtS and Mastodon are sending the search for https://discussions.thenexus.today/topic/16/can-i-bridge-from-nodebb-to-bluesky/12 differently, and NodeBB only handles the Mastodon-style search. This is the kind of situation where your ActivityPub observer could be very useful.

- Mastodon somehow has two different links for the parent post, from the NodeBB side. Maybe this is intentional because they're two different AS fields with two subtly different meanings, maybe it's a bug.

@jon @thenexusofprivacy @julian