You're viewing part of a thread.
You are correct, I can load lemmy.dbzer0.com
I can also see this community there.
The only thing I can assume for now is the delay in federation, I have seen this happening on some large instances.
Thanks for the reverts, so basically if the federation works properly in ideal condition this post shouldnt exist here right ?
As I did edit that (which didn't reflect) and later deleted it as well, but this post still exists here.
So if the federation works well, my post in community of other instance (like this in India News from dbzer0) should also be deleted when I remove/delete it from my profile in Dbzer0. Right?
Correct
Thank you. But seems it still doesn'tworkk properly so I ended up creating this account here for Hinduism and India news mainly as they didn't sync well with dbzer0 idk why
Have you tried to search those communities first on dbzer0?
If you are the first one to search, you will have to search in a special way to allow dbze0 learn about the new community and then sync and federate.
This is true for all lemmy instances, if you are the first one to load the community on the instance.
Might be the case. But in all, welcome brother to lemmy. Hope you enjoy your place here like me.
Yes I did use the link : !community@instance for India news and gave it 12 hours to federate and after that I did the test post here.
Where I faced sync issues like post not being edited and after that it didn't delete.
Even rn there is issues with federation, in the above comment I made a typo where "Thanks for the reverts, so basically if the federation works properly in ideal condition this post shouldnt exist here right ?" Had should instead of shouldn't as typo, so I edited and corrected it.
But this doesn't reflected edited (shouldn't) on lemmy.ml, while it still shows up as should, but all new comments are sync (even this would be)
But it shows perfectly on lemmy.world
And as the original post on dbzer0 was deleted, this entire thing is missing there (which also shouldnt exist here)
I think this issues can be due to heavy migrations overloading servers