From kbin.social, almost nothing is populating from readit.buzz - there’s only one community appearing when searching magazines there using “@readit.buzz”

What’s going on there? Just technical issues with syncing? Having no problem seeing all sorts of content from other instances through readit.buzz, just not the other wy around

  • aaravchen@readit.buzz
    1·
    1 year ago

    Search is basically limited to what’s already federated to or hosted on this server. However if you go find the community you’re interested on another server you can look for it from here with a full “path” and it will start federation to this server.

    When you get the name on another server, it might look like one of the following (could be Kbin or Lemmy. I don’t know if this Lemmy group even exists):

    • https://kbin.social/m/dwarffortress
    • /m/dwarffortress@kbin.social
    • https://lemmy.world/c/dwarffortress
    • /c/dwarffortress@lemmy.world
    • @dwarffortress@kbin.social
    • !dwarffortress@lemmy.world
    • dwarffortress@kbin.social (not common)
    • dwarffortress@lemmy.world (not common)

    In Kbin you would search for these as:

    • @dwarffortress@kbin.social
    • @dwarffortress@lemmy.world

    In Lemmy they would be searched for as:

    • !dwarffortress@kbin.social
    • !dwarffortress@lemmy.world

    Keep in mind that the following apply:

    • your server has to have not blocked federation from the sever hosting the group
    • the server hosting the group has to have not blocked federation from your server
    • if your server has never federated with the other instance before it will say nothing was found, but silently start the federation process in the background. Once it has federated (no visible indication, time to do so is based on server load), the group will show up in search results

    EDIT: add quoting to block autolinking full text
    EDIT2: Clarify federation is opt-out