support Pleroma

[snarfed]

https://gitgud.io/lambadalambda/pleroma . haven't found a website apart from that. doesn't seem to be used very widely. claims to be OStatus compatible.

Known interop problems so far:

• [x] Likes and other interactions with Pleroma posts crash Pleroma
• [ ] Bridgy Fed profiles show up in search results with BF's domain, eg @foo.com@fed.brid.gy, not @foo.com@foo.com. Example: https://cawfee.club/search?query=snarfed.org , click on the People tab

TODO: file issues on https://git.pleroma.social/pleroma/pleroma/-/issues for these ^

[snarfed]

Same Pleroma 500 is still happening: https://git.pleroma.social/pleroma/pleroma/-/issues/3206#note_104956 . Got a bit of a response and discussion from a maintainer in that thread, but no conclusion and nothing more recently.

[hellquist]

When I try to follow my website from my Akkoma account it says "request sent", but I'm not clear on how/where I can see, or respond to, that request.

[snarfed]

@hellquist following up in #374

[snan]

(Moved here)

[snarfed]

@snan feel free to add that to #374!

[snarfed]

Got a new lead here. @diego@lounge.collabfc.com reports:

Pleroma wants to see the ap_id at the top level in either to, cc, bto or bcc. It won't parse into the object to find the ap_id under that.

If I use the json from the Pleroma issue on https://git.pleroma.social/pleroma/pleroma/-/issues/3206 and take the recipient out of the cc and place it into the to at the top level then it works OK.

[snarfed]

Big milestone here! Diego's lead above panned out: for Creates and Updates, it's evidently not enough for to and cc to be in the object, Pleroma evidently also expects the outer activity to have the exact same to and cc values. :shrug: I added that in e2b6b59ff4e451ba0826afaccffd97a888ba1112, and now Pleroma is accepting Bridgy Fed's replies. Example here. Woot!