Yesterday I followed the docker guide for setting up a new KBin instance. Some parts of it are working, but it seems like it’s not federating properly.
What does work:
- I can create new local magazines and threads. They show up in my feed.
- I can search for magazines/communities on other instances and they are added to my magazines list (well about 90% anyway)
- I can (un)subscribe to those communities
What does not work:
- If I visit those magazines from my instance, there is no content. Visiting the community on it’s home instance shows new content since I subscribed to it on mine.
- Searching for my user from something like Mastodon yields no results; however, I can search for and find my kbin.social account.
- I cannot access my newly created magazine from the kbin.social instance
- (This is probably unrelated) Since I made my admin accout using the
kbin:user:createcommand, I cannot create any other users with it.
Any ideas on where I can look to resolve this?
This reported issue sounds a lot like my situation: https://codeberg.org/Kbin/kbin-core/issues/73
You must log in or # to comment.
This looks rather like a discovery issue and is quite common with newly created instances on the Fediverse. You have to search for everything you want for a couple of times before you make your instance aware of the content or other instances aware of yours.
You can more easily overcome this by connecting your instance to an ActivityPub Relay, but I don’t know how this is done on a Kbin instance.
