Hi all, not entirely sure what the issue is here.

I made a community and I got a message from a user from another instance (u.fail) telling me they can’t post threads/comments. I made a quick account to test and when I try it just spins forever on comments, and on threads it seems to go through if I don’t select a language but not if I select English. On the android app I get the message language_not_supported but on both my test user and community itself I have unspecificed and English selected. I also tried a different instance to test and threads/comments seem to go through fine.

I’m assuming it’s an issue with that instance but they can post to other lemmy.world communities fine.

  • imaqtpie@sh.itjust.worksEnglish
    61·
    1 year ago

    This comment seems like it was supposed to be on the post about beehaw defederating. Am I correct?

      • imaqtpie@sh.itjust.worksEnglish
        102·
        1 year ago

        I’ve been trying to pin down exactly what’s happening for a few days. I’m still not quite sure, but here’s what I’ve noticed.

        Sometimes when I’m reading through the comments of a post or drafting a reply, after a certain period of time has passed, the post literally gets replaced at the top of the page with a different post (I believe the other post is always from the same community though). This happens without clicking refresh or anything. So at this point on the page you have a post that you never clicked on at the top, with a bunch of comments below that are actually comments about the post that you DID click on. Additionally, the page will keep updating with new comments. But all of the new comments will be new comments from the new post that you never clicked on. Thus, when you click reply, you end up replying to another post from the same community that replaced the original post you had wanted to reply to. And you don’t always notice, because the comment section you’re reading still has the same comments from the original post for the most part.

        Really fucking weird behavior. I’m hoping the developers are already aware of this and working on a fix.