this post was submitted on 18 Jun 2023
1 points (100.0% liked)

Asklemmy

43907 readers
1364 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

Anyone knows why this happen? Is it intended to work this way?

Here's the link on the lemm.ee instance: https://lemm.ee/comment/225730
Here on the lemmy.world instance: https://lemmy.world/comment/304918

Heres how it's being shown here: https://i.imgur.com/dV5Z68d.png

you are viewing a single comment's thread
view the rest of the comments
[โ€“] MigratingtoLemmy@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (2 children)

I think this is one of the problems of being distributed: since each Lemmy instance needs to sync changes across other Lemmy instances that its users are interacting with, insert activity into its database, have changes made in its local database (the user deleting/overwriting the comment), and then have other instances sync said change in content - the developers say this is dwarfed by traffic to the local database, but when you're connecting to instances across the world there is no doubt going to be some latency. I think a few more minutes and this should be resolved; if not, this is a bug beyond my capabilities of my cursory understanding of Lemmy's technology.

For example:

image

[โ€“] whatyousaidontwitter@lemm.ee 1 points 1 year ago (1 children)

It's probably that plus the issues with instances being overloaded and whatnot. Here hoping that it's a bug or a matter of optimization that can be solved in future updates.