Hi, I’m not sure what I’m doing wrong, but when I try to crosspost from communities on other instances (ie. Lemmy.ml/c/linux) to communities on my instance (sh.itjust.works/c/linux), the local community does not appear as an option. Even when I try to type in the fully qualified community name it will not show up.

This does not seem to happen with every community, and I think maybe it has something to do with a large number of results truncating smaller communities from the list?

If anyone has a workaround or can help me understand how to crosspost better, I’d much appreciate it.

    • CaptDust@sh.itjust.worksOPEnglish
      0·
      14 hours ago

      I think I can do that.

      Nailed it down to CommunitySelectorModal lacks a limit parameter in the search func, and the search api defaults to 10 records returned - not enough. The WebUI appends limit=20 to return more records, which would include my local instance’s linux community. Local community sits at position #11 when sorted by Top.

      I’d also argue that the local communities should be prioritized above the wider fediverse in the results, but that’s probably a point to take up with api devs.

  • _haha_oh_wow_@sh.itjust.worksEnglish
    0·
    5 days ago

    Just out of curiosity: What happens if you wipe app data for Voyager, then log back in and try again?

    Edit: Never mind, I see the comments below.

    • CaptDust@sh.itjust.worksOPEnglish
      0·
      5 days ago

      No change 😞

      This is the full list of communities available to select after I reset data and logged back in. (How the hell does pop_os end up on there?? Heh)