Many fediverse servers can't discover @bsky.brid.gy@bsky.brid.gy

[snarfed]

Getting a few reports of this, Pleroma and Akkoma, not sure what's going on yet. I see the remote instance fetch @bsky.brid.gy@bsky.brid.gy's Webfinger, and BF returns it ok, but then the remote instance never fetches the AP actor id. cc @DeadSuperHero , https://sironi.tk/notice/AhUW5sJtgOzkGdRYG0

[snarfed]

Interestingly @DeadSuperHero says their same Akkoma instance can see @snarfed.org@snarfed.org fine, which is also served by BF. Odd.

[TomCasavant]

I don't know if it's related but I was trying to follow the brid.gy account from my postmarks instance and for some reason it was failing to verify my signature.
I opened an issue with postmarks ckolderup/postmarks#191, since I expect that's where the issue is, but it might be relevant.

[snarfed]

@TomCasavant thanks! Different issue, I'll reply there.

[snarfed]

Merging #998 in here. Evidently this affects other servers too: Friendica, Hubzilla, micro.blog, Wordpress/Friends. Ugh.

@manton, @pfefferle, any thoughts here? Details above

[qazmlp]

I noticed a few things:

In WebFinger, acct:bsky.brid.gy@bsky.brid.gy is aliased to "https://fed.brid.gy/", which doesn't seem right to me since the actors aren't strictly equivalent.

At https://bsky.brid.gy/bsky.brid.gy, the @context includes https://w3id.org/security/v1 twice.
I'm not certain about this, but it may cause some JSON-LD transformers to error out?
https://json-ld.org/playground/ does seem to handle it fine, though.

https://bsky.brid.gy/bsky.brid.gy/outbox errors out with "error":"User bsky.brid.gy not found".

(https://fed.brid.gy/r/https://snarfed.org/ has similar JSON-LD to https://fed.brid.gy/snarfed.org but is missing some parts like the shared inbox? But that's definitely unrelated.)

[snarfed]

Thanks for looking! Useful pionts, but I doubt any are the cause here. None of these should be fatal or block fediverse instances from loading and using the actor. aliases in Webfinger just "identify the same entity;" they're not necessarily AS2 actors, and afaik fediverse instances generally don't look at aliases at all. And I haven't seen these failing servers fetch the actor at all, or outbox, so I doubt they're hitting the others.

[qazmlp]

I found the issue! (for Akkoma)

Akkoma prefers XRD and when reading XRD expects strictly type="application/activity+json" as opposed to strictly type: "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"" when reading JRD.

Bridgy serves only the latter type in both cases, so it doesn't find it.

[snarfed]

Whoa, awesome sleuthing! And very easy fix. Will do.

[snarfed]

I take it back, this is fixable on our end, but not as easily as I thought. And unfortunate because afaict BF isn't doing anything wrong, I don't know that XRD vs JRD should affect the expected type of ActivityPub actor self links in Webfinger.

I can still look into making this change. In the meantime, @qazmlp would you mind filing an Akkoma bug?

[qazmlp]

I can still look into making this change. In the meantime, @qazmlp would you mind filing an Akkoma bug?

Sure, will do, though I think it would be entirely valid to have either type each for one of two rel=self entries in each representation.

[qazmlp]

(The bug is almost certainly upstream in Pleroma… I have to look a bit which software is actively developed right now.)

[snarfed]

Sure, will do, though I think it would be entirely valid to have either type each for one of two rel=self entries in each representation.

Oh, good idea! That would definitely be easier on our end.

[qazmlp]

(The bug is almost certainly upstream in Pleroma… I have to look a bit which software is actively developed right now.)

The Pleroma issue tracker at https://git.pleroma.social/pleroma/pleroma/-/issues doesn't allow sign-ups with (at least) Gmail addresses and I don't have a domain on hand under this identity.

Looks like I can't file this one without jumping through a lot of hoops 😓

Sure, will do, though I think it would be entirely valid to have either type each for one of two rel=self entries in each representation.

Oh, good idea! That would definitely be easier on our end.

It may still be good to file it there eventually since the discrepancy is definitely odd.
To me, it feels like it's probably grown behaviour based on what other instances that support XRD/JRD do.

[snarfed]

I've added a second self link with application/activity+json. @qazmlp, @DeadSuperHero, mind testing when you get a chance?

[qazmlp]

I've added a second self link with application/activity+json. @qazmlp, @DeadSuperHero, mind testing when you get a chance?

I currently only have Mastodon and Pixelfed… I could check with Pixelfed, but that probably didn't have this issue in the first place… It worked and immediately got search-indexed! That went smoother than expected.

[snarfed]

Great! Also @manton reports that it's visible in micro.blog now too. Promising!

[ObjectInSpace]

I'm on an akkoma server and my bluesky account (which is following ap@brid.gy) wasn't showing up... until just recently. Thanks for that! I still am not seeing actual content in my feeds though. I'll try re-following.

[snarfed]

@ObjectInSpace thanks! BF bridges posts going forward, but not necessarily historical ones.

This post is about whether you can see @bsky.brid.gy@bsky.brid.gy from some fediverse servers like Akkoma though. Could you see if that account is visible for you?

[ObjectInSpace]

I can search for @bsky.brid.gy@bsky.brid.gy and read the profile and request to follow, but it says that the follow request is pending. The same is true if I search for my bluesky handle on the fediverse side. I'm following ap@brid.gy from bluesky but my fedi handle is not searchable on bluesky and new content from fedi doesn't appear on my bluesky. The exception is replies to my bluesky posts, which show up in my bluesky notifications. bluesky posts do appear on akkoma and I can boost them from there, which show up as reposts on the bluesky side. This allows me to follow my fedi handle from bluesky, which shows me boosts+replies to my bluesky, but nothing else at present.

[snarfed]

@ObjectInSpace what are your fediverse and bluesky accounts?

[snarfed]

Sounds like this may be the Bluesky polling delay. We're working on improving this in #978.

[ObjectInSpace]

Yeah my bluesky posts did eventually show up fedi-side, they were just delayed. Editting/consolidating comments to be less spammy. My handles are drew@akkomane.social and prism@bsky.social if they are still helpful.

[snarfed]

Got a confirmation that Pleroma can now see the bot user too: https://sironi.tk/notice/AhbtQ7x9AqiRF7UoaW . Tentatively closing.