The lemmy.world bubble is back
For the past days I've noticed that posts/comments I make on my lemmy.world account are not (or rather very slowly, if ever) federated to the source instance of the community and post/comments that are on the source are not (or rather very slowly, if ever) federated to the local copy on lemmy.world.
The result is again (as it was before 0.18.1) that lemmy.world users are living in a bubble in which they see each othery posts/comments but nobody else does.
Is this a known issues and is this going to be addressed?
17 replies
Do you have some examples we can look into?
I'm not the OP, but I have an example from two days ago posting to a community hosted on feddit.uk:
My comment is https://lemmy.world/comment/1718032, which is present for lemmy.world, but not for feddit.uk
I haven't posted any comments since, so I don't know if it's a one-off thing.
Beehaw's defederation of lemmy.world doesn't seem to be involved in this one.
I have noticed comments made in a community here on lemmy.world not appearing over on feddit.uk too.
https://feddit.uk/post/809693
https://lemmy.world/post/1995177
But they do show over at lemm.ee
https://lemm.ee/post/1801137
Maybe more of a feddit.uk issue?
My example did not make it to lemm.ee either, so it would not have been exclusively a feddit.uk issue.
I would be really handy for finding out what's going wrong if there were some way to track the history of a posting as it propagates across instances, but I'd imagine that would be quite tricky to do. On the other hand, perhaps these cases simply correlate with downtime either at the origin or at the receiving instance?
No federation from source to
lemmy.worldlemmy.world: https://lemmy.world/post/2219417No federation from
lemmy.worldto sourcelemmy.world: https://lemmy.world/comment/1749875Note that I pulled my post to the source instance by searching for it from there, but updates/edits are still not federated. This post also has a reply from a
lemmy.zipuser which hasn't been federated tolemmy.worldyet.Ah. The comments are made by Beehaw users, and Beehaw has de federated from us.
So the post from .wtf will arrive here but the Beehaw comments won't
I thought
beehaw.orgdefederating from us would not affect post/comments on shared source instances, e. g.lemmy.wtf, which is neither defederated frombeehaw.orgnor us:https://lemmy.world/post/149743
https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md#the-announce-activity
Cloudflare Challenge?
Since
lemmy.worldis now behind Cloudflare, is it possible that federation is hit by Cloudflare Challenges as described here?It's not a defederation issue (this time) as the examples have shown which leaves me no choice but to finally leave.
lemmy.worldis just too big for its own good. Good Bye! and Good Luck!P. S.: @[email protected] Is it possible to lock an account instead of deleting it so that posts/comments stay?
Lock this account here, I mean.
@[email protected]
I think I could ban your account without deleting content, but maybe that's not what you want?
No, I meant lock as in disable login, remove email address, 2FA and freeze all content. This feature might not yet exist in lemmy but it probably should be implemented. Apart from a user leaving this might actually be required to properly handle a user passing away.
I agree that should be added. But I meant for now, permanent ban without deleting content is the closest to that. Other than that, the only option is to delete your account which should delete the posts too. (But even that doesn't always work...)
OK, then I just wait and stop using this account until such feature gets implemented. Deletion is not an option as it would also delete all posts/comments. At least local ones, maybe even posts/comments on other instances. Dunno, if the User/Delete Activity is propagated to other instances (yet).
Bye and Thanks for all your hard work!
Interesting