For example this comment: https://lemmy.sdf.org/comment/984558 and this post: https://lemmy.sdf.org/post/873681 I both deleted, however from other instances they still appear to be there.

In case of the post others can still interact with it (comment and vote) except me, OP. In case of the comment, it just keeps the original text instead of deleted by creator, it can be interacted with, but it is also accessible to me as OP.

This is how the comment and the post appear from lemmy.ml. Still there, alive.

Edit: As per other lemmy user, this is already a known bug: https://github.com/LemmyNet/lemmy/issues/3588
The comment: https://lemm.ee/comment/1133649

    • RoundSparrowEnglish
      5•1 year ago

      For posts, I have been working on it this week and found that it has been broken since June 23 commit. Posts don’t even get removed on the home server with 0.18.2, a fix is already waiting for acceptance: https://github.com/LemmyNet/lemmy/pull/3613

      As for comments, with 0.18.2 - it depends where the delete is done. If you are on a remote instance from the community, the comment will be deleted on 2 servers, but no more. The local instance you use will delete, as will the community home, but it seems to me there never was any code to distribute deletes to subscribed servers: https://github.com/LemmyNet/lemmy/issues/3625

      It also impacts moderators removing posts and comments. As these internally are similar to deletes. !asklemmy@lemmy.ml is one of the communities that has a lot of moderator removals due to people confusing the purpose of it as a technical support forum, and you can see servers not getting the mod removals frequently.

  • @HangingFruit@czech-lemmy.euEnglish
    4•1 year ago

    Not issue with Memmy, but lemmy itself. This is how it works. It needs time to propagate into other instances. And sometimes even the propagation can fail.

    EDIT: this is not about Memmy. Misread the community. The second sentence still stands.

    • RoundSparrowEnglish
      3•1 year ago

      It needs time to propagate into other instances.

      Since 0.18.2 has been deployed by the bigger servers, the speed of propagation is really not much of an issue. The problem is a bug was introduced for posts on June 23, and for comments it seems that perhaps it has never worked. See my other comment for details.

      • @HangingFruit@czech-lemmy.euEnglish
        2•1 year ago

        I see, thank you for the correction. I always thought that it needs time to propagate. And if it fails, I read somewhere that there is no handling in place, so it falls into void.

        • RoundSparrowEnglish
          2•1 year ago

          And if it fails, I read somewhere that there is no handling in place, so it falls into void.

          That is true in the current design, but in studying the actual outcomes, delivery-failures are not happening nearly as much as the problems with deletes and moderation.

          I’ve been comparing servers for posts and comments for weeks, with 0.18.2 versions in the field - the majority of current inconsistencies are logic problems in the code that never even attempts to send (like deletes only going to 2 of 50+ servers).