this post was submitted on 07 Jun 2023
73 points (97.4% liked)

Lemmy.World Announcements

29077 readers
147 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world/

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

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.
you are viewing a single comment's thread
view the rest of the comments
[โ€“] godless@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (2 children)

Issue:

So, I've created !childfree as a local community, seemingly normal. Only, it doesn't seem to be accessible to anyone locally.

Meaning, https://lemmy.world/c/childfree gives me a 404. Instead, I have to open it as https://lemmy.world/c/childfree@lemmy.world - initially I thought maybe I had made an error creating the community and added the instance, but trying to replicate it shows that @ is not a permitted character, so the problem must have come from elsewhere.

From other instances now I can access it just fine: https://latte.isnot.coffee/c/childfree@lemmy.world or https://feddit.de/c/childfree@lemmy.world (where the @instance is the default behaviour). Locally however, that should not have happened.

Even if I enter the community locally, and click on the !childfree just below the name of the community, it gives me a local 404 (see below).

Any idea what's going on here, and how to resolve the problem? Since we are redirecting users from our sub here, it's creating quite some headaches... And apparently users trying to subscribe from other instances also don't see any posts for up to 48h (tried that myself).

Edit: Apparently I cannot access the community via feddit.de. The other one works fine though - I do have accounts on either instance.

[โ€“] Gecko@lemmy.world 2 points 1 year ago (1 children)

Same with https://lemmy.world/c/titanfall

https://lemmy.world/c/titanfall@lemmy.world works
https://lemmy.world/c/titanfall does not and gives a 404

And similarly when going via feddit.de, i.e. https://feddit.de/c/titanfall@lemmy.world I can see the community but only 1 out of the 2 posts.

I think OP comment and my issue are related. What can we do to help investigate this? I was planning on moving over a community from reddit and this is unfortunately blocking it. If I can help in any way to figure this out and resolve it, I'd be more than happy to do so <3

[โ€“] godless@lemmy.world 1 points 1 year ago

Yep that seems to be exactly the same issue indeed. Very weird.

[โ€“] Hhffggshn@lemmy.click 1 points 1 year ago (1 children)

Thanks for working on this.

FWIW, I'm on lemmy.click. When I search for this community on my instance using https://lemmy.world/c/childfree or !childfree@lemmy.world, I don't see the community in the search results.

[โ€“] godless@lemmy.world 2 points 1 year ago

Yes, something weird is going on. Being new to lemmy I initially assumed it to be a configuration error on my end, but that doesn't seem to be the case, I've been trying everything for the last 24h or so.