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.
As others said, it doesn’t support the domain rn. PRs and issue reports are welcome 🙏
I think I can do that.
Nailed it down to
CommunitySelectorModal
lacks alimit
parameter in the search func, and the search api defaults to 10 records returned - not enough. The WebUI appendslimit=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.
Ohh, I think the local communities show up but without the domain.
Like this:
The search/dropdown is a bit janky imho, both there and in the modlog.
Yeah, I can open the post in the WebUI/Browser and share that way. That’s been my approach for the moment - but just community “Linux” (local) doesn’t seem to appear on Voyager’s list the same way. I think it’s an issue with this app specifically, not lemmy or the instances.
Thanks for taking a look!
yup, just tested this… which is indeed in the local community
https://sh.itjust.works/post/27424100 (now deleted)
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.
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)