Pleroma doesn't support Social Inbox

[fauno]

By looking at Pleroma's code I think it's validating that the origin of the action is the same as the actor, and since the actor is at Sutty but the action comes from DPress, it fails:

https://git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/web/federator.ex#L85

https://git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/object/containment.ex#L67

That would mean that sites need to reverse proxy DPress to actually work?

Originally posted by @fauno in https://github.com/hyphacoop/social.distributed.press/issues/9#issuecomment-1709394728

[RangerMauve]

Cool, so we have several options here:

• get Pleroma to allow other domains
• do manual approval of follow requests from the publisher by sending the Accept/Reject activities from Sutty
• Have the inbox send the activity to the publisher and wait for it to be published before notifying the follower of the activity
• Set the id to be from the actor, but don't bother actually publishing the activity (might not work if the ap instance tries to validate?)

I think the middle two are the "best" options but they add more complexity on the publisher side.

[fauno]

do manual approval of follow requests from the publisher by sending the Accept/Reject activities from Sutty

this means they need to be created by the plugin? and probably rebuilding via webhook