I'd like to bridge this account to Bluesky using #BridgyFed but am not sure how -- it's not obvious how to follow @bsky.brid.gy@bsky.brid.gy ... so maybe I'll start by making this post tagging it and see if it works?

CC @thenexusofprivacy@infosec.exchange , an account I know is bridging

@jon Hmm, I didn't get the notification. ANd when I look at the message, @bsky.brid.gy isn't a link to the account which is kind of weird. What happens if I reply?

I'll tag @jdp23 as well just for luck.

Oh dear,the original post from @jon didn't federate -- even though I was following the account.

@thenexusofprivacy

@thenexusofprivacy@infosec.exchange Your message federated here (although didn't get a notification) and @bsky.brid.gy@bsky.brid.gy was tagged correctly but when I click on it, instead of bringing up the profile page, it brings up the JSON document at https://bsky.brid.gy/bsky.brid.gy

@snarfed@indieweb.social @snarfed.org @julian@community.nodebb.org any idea what's going on here? The thread as a whole is at https://discussions.thenexus.today/post/48

EDIT: there are a couple of different issues here:

• weirdness with @bsky.brid.gy@bsky.brid.gy UPDATE: Julian's looking at this
• missing notifications in both directions with @jdp23@indieweb.social and @thenexusofprivacy@infosec.exchange (UPDATE: this was a nodebb bug that's been fixed)
• the original post unexpectedly not federating to indieweb.social (maybe a separate problem?)

@jon Your reply to the post from @thenexusofprivacy that I was tagged in *did* federate here. But, I didn't get a notiffication.

@jdp23@indieweb.social the notification thing was a bug we fixed this week. Turns out it was a bug in NodeBB causing Mastodon to crash. Fun!

I'll look into why the bridgyfed actor doesn't assert properly.

@julian thanks!

But with, why didn't your reply to me federate over into the thread on discussions.thenexus.social?

@jdp23@indieweb.social doesn't look like @jon@discussions.thenexus.today follows me

But my mentioning that account should work now.

@jon@discussions.thenexus.today just updated you to the latest, can you try the bridgy tests again?

@julian@community.nodebb.org yep. I'm not sure how to get to @brid.gy.fed@brid.gy.fed's profile by searching, but I'll try tagging it here and see how it loops.

(Also apologies for not following you, fixed now!)

@julian@community.nodebb.org no, I still get the same behavior -- it's not highlighted as an acount when it renders, so no link to click on.

All right, let's try this again ... and see if it works better. Can I tag @bsky.brid.gy@bsky.brid.gy

CC @thenexusofprivacy@infosec.exchange , an account I know is bridging, and @julian@community.nodebb.org

EDIT: nope, still can't tag @bsky.brid.gy@bsky.brid.gy

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

Similar search results on blahaj.zone (which is on Sharkey)

searching for https://discussions.thenexus.today/post/52 works

searching for https://discussions.thenexus.today/topic/16/can-i-bridge-from-nodebb-to-bluesky/12 gives an internal error in Sharkey, oh dear.

Also GoToSocial strips the subject header out in replies, as does Mastodon.

@nexus@gts-test.thenexus.today @jon@discussions.thenexus.today @thenexusofprivacy@infosec.exchange @julian@community.nodebb.org

Hi @jdp23@blahaj.zone, can you try again here on the NodeBB community? I made a small change that should allow you to properly find the bridgefed user to start the bridge.

I don't know any bridges bsky accounts to test, could you let me know one?

@julian @jdp23 you can test with any of my bridged accounts if you'd like:

@wake.st is my bluesky account thats bridged to fedi

@wakest is my #wafrn account thats now both a bluesky and ap account simultaneously

@liaizon@social.wake.st thanks! Seems like I'm already able to see those accounts and they already have posts. Good sign.

@wake.st@bsky.brid.gy did you get this message from bsky?

@julian @wake.st hmm no I didn't get that message but I also didn't get my own mention so maybe the bridge is down or lagging atm

@liaizon@social.wake.st did that message ever show up?

OK, let's start by seeing if I can tag @fed.brid.gy@fed.brid.gy ...