Hi,
I’d like to understand, because I can’t find it in the docs: How do the membership-settings influence the behaviour of activitypub?
Example: My website does not need Membership-management right now. So I disabled it.
All pages are public.
But: When trying to follow the handle with a Mastodon-client (like IceCubes), I get after a time only the feedback: “Follow requested”. And I cannot see the example note I posted.
Is this a genral configuration issue of my self-hosted Ghost instance?
How does this all work together?
1 Like
@ppuschmann is your Ghost self-hosted? And if it is, are you getting the problems described on ActivityPub self-hosted isn't quite federating ? The problems you describe look familiar. In my case, I believe they had nothing to with membership settings but with self-hosting ActivityPub.
1 Like
Yes, it is self-hosted.
And apparently this is sort of a mess right now or it hasn’t really matured. ¯\_(ツ)_/¯
1 Like
It is important to mention that this forces the self-hosted Activitypub implementation to connect to the Ghost AP, so it technically stops being self-hosted as such.
1 Like