The app updated itself to the new version. Now it seems that almost any action with the api gives a timeout, or the message “please refresh”. Upvoting and other actions give similar results: often doesn’t go through.

Is there something we should clear when updating?

I’m at @world and the server just got patched yesterday, maybe related? Although I was browsing Lemmy with Mlem yesterday without any noticible issues.

That said: I had issues posting this with Mlem, and I had to login a bunch of times in safari. Maybe @world still has some issues

  • vinnymac@lemmy.worldEnglish
    31·
    1 year ago

    I am experiencing this as well. I had to sign in to another account, and then switch accounts back to @world to get Mlem to pull down posts again. Definitely something funky going on with the API in this build 🤔

    • Mereo@lemmy.caEnglish
      3·
      1 year ago

      It’s probably due to Lemmy.world returning error 502 this morning. I’m on the lemmy.ca instance and Mlem is working perfectly.

      • Gompje@sh.itjust.worksEnglish
        1·
        1 year ago

        It was!

        I could create another account on .works to reply and post it was just a coincidence. But still work happened in between and it took a bit for me to be able to state just that… haha I look like a total n00b now. ¯_(ツ)_/¯

        Anyway: app is indeed fine. .world is still having some issues but Ruud will do his best.

  • adj16@lemmy.worldEnglish
    2·
    1 year ago

    Y’all, lemmy.world is having the issues, not Mlem. Poor ruud has probably been running from one server on fire to the other ever since The Great Reddit Exodus really kicked into high gear on the 30th/1st

  • Gompje@sh.itjust.worksEnglish
    1·
    1 year ago

    It’s due to Lemmy.world having issues. I know that now. I created another account in .works and that is working fine.

    It’s interesting to see that this post has -1 and a few comments but on .world it’s a total different story.

    Again: it had nothing to do with the app itself.

    Suggestion: maybe add something as “the server @world is having issues atm” or something like that?

    Both things happening at once totally threw me off and I only realized it was the server after visiting the website. And I’m not a n00b. Think it was probably b/c I had stability issues with the app before (not related to the server)