How does this work on kbin at the moment?
My understanding is that, at least on Lemmy, you should be able to search for a full community name, wait a while, and have it show up and start federating. I’ve been searching for two communities (in the format name@instance.tld) on kbin since yesterday and it still shows no matches.
Both are small (<20 subscribers) and currently inactive (no new posts in a week). Do I need to wait until there is new content in them?
Search like this: !name@instance.tld
I don’t think that works on kbin. If I search for a big community like “science@beehaw.org” I find it immediately, but “!science@beehaw.org” gives no results.
The way to do it in kbin is to go to the magazine section specifically. The normal search doesn’t find magazines I believe. Then search in the following format:
syncforlemmy@lemmy.world
. I use that as an example because I had to learn this very thing a few minutes ago.That’s exactly what I’ve been doing maybe 15 times since yesterday. It finally worked earlier, but according to a top comment you should not use the magazine search if the magazine doesn’t already exist on kbin.
Good to know. Thanks!
Ah!
And if you search for the original community url? For example: https://beehaw.org/c/science
Haha, uh, it did find a community when I searched for the URL, but it found science@mander.xyz – that’s pretty bizarre.
I think this is either a bug (I mean, in one sense it’s certainly a bug) or just that something needs to change in the community before it shows up and is created locally (which kind of is a bug too).
If the kbin codebase wasn’t so complex I’d try to check the code to see how this all works.
it’s probably related to the bug that is known about and getting fixed - that kbin is currently case sensitive - which breaks things a bit when it comes to remote communities.