Seems to me the fear of overloading one instance over another will not happen after all.
But I do hope the Threadiverse can hit 500,000 consistent active users by the end of summer.
Give me that hopium guys! 💉
Seems to me the fear of overloading one instance over another will not happen after all.
But I do hope the Threadiverse can hit 500,000 consistent active users by the end of summer.
Give me that hopium guys! 💉
Probably because lemmy.world stops working with half the apps every other day. Some days I can only use it with Thunder, other times only Jeroba, other days it works with every app except Liftoff. There’s just no predictable pattern to it and I’ve found myself just avoiding lemmy.world lately because I don’t want to type out a 3 paragraph comment just to find that my app isn’t logging in to lemmy.world today.
heh, would you look at that. It won’t let me post this comment on Jeroba so I had to log in with a browser. This is fuckin bullshit. I’m going back to sh.itjustworks until this gets fixed.
If it’s the same issue as me, you just need to logout/login inside the app. JWT secrets had to be rotated following a recent exploit, and the apps I’m using haven’t accounted for this case. Liftoff still thought I was logged in for example, but as far as the instance was concerned I wasn’t. No issues after I logged out/in manually.
For a few days my jerboa was logged out every time I went to use it.
Bummer, I think it should be all good now that the initial problems with updating the instance and closing the exploit vulnerability are sorted though.
Other than being signed out twice I haven’t had any issues using wefwef
I think those instances we planned as I have had the exact same experience. App update and login again is a small price to pay for not having to live under the boot of capitalism!