Ryan Barrett

np! re why www isn't working, as mentioned earlier, bridgy fed is currently mixing www and naked domain when it talks AP: > however, note that the `actor` in the...

I've been looking at this more, and i think i was actually wrong before. the `id`of the activity we send is indeed the naked domain even for a follow of...

interesting! took me a couple tries to understand the request, but i get it now. not a priority for me, but i'd probably accept a PR. feel free to tackle...

Fun, thanks! Bridgy Fed is pretty different, we couldn't add this directly, but it's great to have another example.

thank you @swentel! great sleuthing, really useful info. and funny coincidence, i've been troubleshooting Pleroma compatibility in Bridgy itself recently too, eg https://github.com/snarfed/bridgy/issues/977 .

Thanks for the details! Here's also the complete AS2 activity that Bridgy Fed sent to https://social.nipponalba.scot/users/jk/inbox , and got a 200 back for, [from Bridgy Fed's log](https://fed.brid.gy/log?key=https%3A%2F%2Fjk.nipponalba.scot%2Fresponse%2F6048bcde%2F+https%3A%2F%2Fsocial.nipponalba.scot%2Fobjects%2F1bf56236-fe1f-4f3c-9978-7b3eabcf73b5&start_time=1615384462). One thing I...

I've added an id to outbound AS2 activities. Feel free to try again!

@jk-na those are all good clues! I did notice one other quirk: it looks like your site's redirects to Bridgy Fed are duplicating the query parameters. eg `https://jk.nipponalba.scot/.well-known/webfinger?resource=acct:[email protected]` currently redirects...

Also, `Couldn't parse XML` is odd. ActivityPub is all JSON afaik, the term XML literally doesn't appear anywhere on https://w3c.github.io/activitypub/ , so I'm not sure where Pleroma is expecting XML.

Based on the logs, it looks like Pleroma is trying to parse the JSON WebFinger response as XML, which explains that error and why it can't find or validate your...