Sorry if this seems like a silly question but I have noticed over the last few months my feed(?) has started to act odd.
No matter what I do I don’t see any posts from .world. I checked and mander does not seem to block .world (kinda why I liked this instance) and even weirder is how my feed gets filled with mostly .ml posts with almost no activity no matter how I sort.
This did not happen before and got me thinking, I don’t even know how this works across federated instances.
Does anyone know:
-
How does the sorting work on an instance? Is it all the same no matter what instance it is?
-
Did anything change in the last few months, that would cause all .world (and I assume others) posts to not show?
-
Other then changing instances what can I do to mitigate the weird slanted results?
Thanks for the reply (I was worried no one would) but would that cause the weird behaviour I am seeing? The timing does not seem to match but it could make some sense.
If what you are saying is the cause then Lemmy as a federated whole may now be effectively split up due to sync issues?
Actually there are some comments from other people: https://reddthat.com/post/20632337?scrollToComments=true
Most of them are from LW, so they won’t federate before a few days.
The issue is that if one instance has too many updates to send to another one (in this case LW to mander) it starts to create delays.
This mostly happens due to LW size, as you can see Reddthat has no issue
Oh wow, yeah its like night and day. Well now I guess I have to figure out a fix.
Sad times if I have to find another instance, again.
Any ideas what can be done longer term to address this (in general)?
Since I can’t see anything here I will check on .world
This bas to be adressed by the mander admins.
For instances, i would suggest lemm.ee or sh.itjust.works
Maybe I should just crosspost this to !mander@mander.xyz
Mander is not the only instance having this issue. Other instances like lemmy.nz (it was), reddthat also aussie.zone, monyet.cc have similar issue since months ago. I assume the culprit is cogent’s de-peering drama not from lemmy itself.
https://www.thinkbroadband.com/news/9896-ntt-cogent-peering-dispute-increasing-latency-for-some-routes
https://www.reddit.com/r/networking/comments/1cu13bv/cogent_depeering_tata/
And those lemmy instances are hosted in APAC.
Also you can check federation issue with this
https://phiresky.github.io/lemmy-federation-state/site?domain=lemmy.world
And if I’m not mistaken our admin has solution regarding the issue a while ago, you may ask Dave.