Seriously, I haven’t been able to post a thread from my main account recently because of this.

    • Roundcat@lemmy.caOP
      3·
      1 year ago

      I really want to like it too. The UI experience on kbin has been good enough that I have stuck around despite the issues. Plus I like the culture of the site and the users I share it with. It would be a shame to leave it.

      But this glitch in particular has really hampered it’s usability for me, and has me thinking if I should have my primary account elsewhere until thinks get more reliable there.

  • haohao@lemm.ee
    1·
    1 year ago

    When I use my kbin account I get the same error, but when I go back to the magazine the thread has been posted. Edit: same with photos/pictures

    • Roundcat@lemmy.caOP
      1·
      1 year ago

      Commenting has been fine, but posting threads on the otherhand has been broken for me over the past 24 hours, and its affecting some other users as well, though it might not be affecting everyone.

      What happens is I’ll post a thread or a photo in a community, and get this error message. I refresh, the post appears in my profile, but not in the community I posted in. I’ll get some other weird glitches too, like after some time passes, it becomes visible to others, I’ll get replies in the thread, but won’t be able to see them or reply, and so on.

      I’ve encountered bugs on kbin before, but this one has been the most devistating cause it affects my ability to even post content. Before I would only get this error when upvoting on some threads, or when I tried to block a spammer.

      • GeekFTW@kbin.social
        1·
        1 year ago

        though it might not be affecting everyone.

        Can confirm it is not affecting everyone. Posted numerous threads yesterday with zero issues. I have gotten this error numerous times when trying to block or upvote as you said, though not for the last 4-5 days or so for me.

    • kopper [they/them]
      4·
      1 year ago

      kbin.social is getting too big with an admin that’s asleep on the wheel (just like every other flagship instance on fedi (yes even mastodon.social)) and kbin the software is still too immature and is in the same “putting out fires” mode lemmy was in back in 0.17.x “peak reddit migration” era