Interesting. I'll investigate and get back to you.
this post was submitted on 17 Jun 2025
4 points (100.0% liked)
Europe Pub
119 readers
1 users here now
founded 3 months ago
MODERATORS
@nordiesta@europe.pub I've created a bug report on the Lemmy GitHub project. I'll get back to you as soon as the issue is resolved!
@nordiesta@europe.pub It should work now.
However, there's a known issue when fetching communities by name if a user account exists with the same username. Lemmy uses the ! symbol for both usernames and communities, which causes ambiguity.
To avoid this problem, you should use the full community URL instead of the !name@instance format when searching. This ensures the server correctly interprets your request as targeting a community rather than a user.
Examples:
- !raining@sh.itjust.works → https://sh.itjust.works/c/raining
- !pixelart@retrolemmy.com → https://retrolemmy.com/c/pixelart
- !Eevee@pawb.social → https://pawb.social/c/Eevee
Using the URL format avoids confusion and ensures consistent results.
Thankz for resolving the issue 🎉 The comms show up now, What exactly did you do to get around this issue from upstream if you would like to answer. It might be helpful for admins of any other instances who experience this problem and by chance find this post!
I've removed the blocked URLs for now. There is currently a bug which should be fixed in the next version.
More information here: https://github.com/LemmyNet/lemmy/issues/5802