Lemmy.world Support

3202 readers

2 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket

You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

founded 1 year ago

MODERATORS

[email protected]

Problem federating with other instances? (lemmy.world)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Hi,

I normally post from an account on the sh.itjust.works instance and recently noticed that posts and comments to and from lemmy.world are getting delayed by a few hours.

I made this post (https://sh.itjust.works/post/17275496) to discuss on that instance, but you might not be able to see the comments over there, including responses from the admins, if you're using a .world account.

Full disclosure, I am not on the admin team over there, but based on their responses it sounds like something might be going on with the lemmy.world side.

Just wanted to bring it to your attention.

Thanks

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago)

I'm having this problem as well, as of the last ~20hrs

[–] [email protected] 1 points 7 months ago (1 children)

I´m having a similat Problem with:

https://lemmy.world/c/[email protected]

There is a post Tha should be pinned. In the original instance it is. Over Lemmy.World not. Other instances see the pinned post correctly

[–] [email protected] 2 points 7 months ago

Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]