Added some more known isues
Added some more known isues
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 pl...
I added some known issues with websockets / spinning wheel to the known issues post
You're viewing a single thread.
Is outbound federation a known issue?
I've just tested inbound from sh.itjust.works and it was instantaneous. But my outbound posts that have worked take hours and none have succeeded for days.I dunno. Can't see any of that in Lemmy. So I'll have to test if it's our outbound or sh.it's inbound.
I've been having outbound federation issues from lemmy.world with both kbin.social and my personal Mastodon server, social.goodanser.com. I've also had people report to me that posts and comments are not showing up for them on feddit.de.
Understood. I'm not just trying to get content to sh.itjust.works, though. outbound from here to .ml, kbin, and fedia have all failed. I'll test kbin inbound.
kbin is not instantaneous. It has not appeared and I assume, due to instability, is likely lost. If it comes through I will update with time.
The kbin test comment posted there 4 hours ago according to time stamps. So 5 hours from previous comment
I’ve had problems with posts not showing up on sopuli.xyz, so I’m guessing outbound.
yeah, I've got multiples not making it through.
sh.itjust.works to .world is istantaneous, posts and comments. other way is failure. but, sh.itjust.works to kbin.social also has either failed or is taking a long time. But that connection might not be as established.sh.itjust.works to lemmy.ml test was instantaneous for a comment.
so something is amiss here
Here’s one of the posts I think never made it through: https://lemmy.world/post/300681
Here’s a similar report, this time with feedit: https://lemmy.world/post/440406
Top comment by @[email protected] says the new version coming tomorrow fixed this issue. Guess we’ll see.