According to the support Community this was fixed about an hour and a half ago, but I continued to have issues I had to manually log out again and log back in to fix it
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.
lemmy.world is bugged right now. What I did is backed up my account subscriptions/settings and imported it over to sh.itjust.works. You may need to try a few times (it'll tell you when it's successful).
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.
Summary: Attacker found a way to inject JavaScript into the sidebar, letting them steal auth tokens ("JWTs"), including from an admin account. They then used the stolen admin access to vandalize the site. At one point, the attacker used the stolen admin account to falsely announce that the attack had been remediated. Later that day, the attack actually was remediated by the site owner (Ruud) and the vulnerability was patched in the Lemmy code.
Lemmy has been improved at light speed over the last couple of weeks. When I joined around 3 weeks ago everything felt prototype-like. But now lemmy.world back-end with Voyager front-end feels almost like Apollo quality. At this rate, it definitely will, in another couple of weeks.
Memmy signed me out (covertly - only way I could tell is my subscription view showed communities wasn’t subscribed to). Re-entering my credentials fixed it. Let’s see if this posts first time.
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. :)
Just setup my own Masto server for myself. My initial thought was, "Crap, I can't follow anything by hashtag anymore," since I'm the only user and nothing would get pulled in by federation.
Then I learned about using https://relay.fedi.buzz to create a whole bunch of relays based on hashtags. And now it's pretty much perfect for how I use it.
My federation feed is just stuff I like, and my server doesn't get filled with random crap from federating with hundreds of full-ass servers like typical relays give you.
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.
Logging out and back in only really fixes the "youre logged out" (not entirely though) issue. Posts still have to be posted multiple times for it to actually happen most of the time from my experience.