Why am I signed out every time I open this? Why can I hardly post anything anywhere? It’s like a dice roll.

  • fury@lemmy.worldEnglish
    1·
    1 year ago

    Reminds me of when I had to change my site’s login cookies from “session” cookies to “persistent” cookies because mobile browsers aggressively clear the session. I don’t know if that’s what was going on in this case.

  • fubo@lemmy.worldEnglish
    0·
    1 year ago

    Server-side authentication bug; maybe fallout from the recent attack? I’d expect instability for the next day or so as auth & related problems shake out.

  • Gutotito@kbin.social
    0·
    1 year ago

    Getting federation working as advertised is a pain in the ass. I ran a solo instance back when Mastodon was new, and there was no end to the nonsense it generated. That’s why I’m now subscribed to the instance @ernest is running. :)

    • wpuckering@lm.williampuckering.comEnglish
      1·
      1 year ago

      I guess they don’t really know what they’re doing and are learning how load balancing works on the fly, and thinking that’ll result in HA without side-effects without further work.

      EDIT: Don’t really get why this was downvoted. With the proper technical knowledge it’s clear to anybody that two instances with different JWT secrets behind a load balancer is going to cause this very issue. So the fact that they set it up that way means they have a knowledge gap (“they don’t really know what they’re doing”). At the very least they should enable sticky sessions on the load balancer if they insist on going this route, which would mitigate the issue (but depending on client-side configuration would not necessarily prevent it completely).

      Don’t take this as an insult towards the admins of the instance, I’m just pointing out there’s a lack of knowledge, and some trial-and-error going on.