In this post I will list the known issues or possible improvements for Lemmy.world.
Please comment with any issue or area for improvement you see and I will add it here.
Issues can be:
- Local (lemmy.world) (also performance issues)
- Lemmy software issues
- Other software related (apps/Fediverse platforms etc)
- Remote server related
- (User error? …)
Known issues
- Posting big posts of over 2000 characters fails, the Post button will stay spinning
- Top posts page gets a stream of new posts ? Websockets issue
- You’re suddenly in another post than you were before > Websockets issue
Enhancement requests
- Can themes be added? > To be checked if this can be done without changing code.
Certain communities seem to be inaccessible from Lemmy.world and vice versa. For instance, if I try to access /c/boston in Lemmy.ml via lemmy.world/c/boston@lemmy.ml, I get a “404: couldnt_find_community” error. Similarly, trying to access /c/boston in Lemmy.world from either Kbin.social (via kbin.social/m/boston@lemmy.world) or Lemmy.ml (via lemmy.ml/c/boston@lemmy.world) both give 404 errors.
I’ve observed the same thing, newer lemmy.ml communities and pretty much everything from kbin returns 404 when accessed through this instance. It happens with other instances, to a varying degree, mostly with lemmy.ml. However !fediverse@kbin.social is accessible from beehaw but 404s from lemmy.world.
Strange! Does that possibly mean there’s an issue with federation on the lemmy.world side?
Hmm works for me, I can find it and open it. Maybe lemmy.ml was overloaded?
Yeah possibly! I think the second issue I mentioned is still occurring, though. Namely, lemmy.ml/c/boston@lemmy.world returns a 404 error (and also for Kbin.social).
Then I think lemmy.ml hasn’t discovered it yet, maybe there’s delay on their server?
Perhaps! This should be triggered by searching “!boston@lemmy.world” from lemmy.ml, correct?
Yes, but as the server is overloaded, it might take some time.
Sounds good, I’ll check back another time, thanks for looking into it!
Yes