Why am I signed out every time I open this? Why can I hardly post anything anywhere? It’s like a dice roll.
We beta testing
Betta believe it
I mean, we literally are. They have been very clear about that.
Every time they upgrade their servers you gotta re-login.
Login issue reportedly fixed with 0.18.2 update: Lemmy.world updated to 0.18.2
Good to know! Looks like the login/out issue stopped.
I heard it is a load balancing issue. Lemmy World has two instances, with two different JWT secrets, and you have a 50/50 chance of hitting the wrong server when you make any API requests.
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
Great!
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).
Lemmy.world when I tried to post kept saying not logged in. Created an account on sh.it just.works
e: This instance hardly has anything
You can access all your lemmy.world communities from sh.itjust.works, it doesn’t really matter if it has much locally.
Only issue is it’s hot feed seems bugged
Thank you for the tip on backing up.
I have also experienced some bugs. So now I have more accounts
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.
Attack? I am outta the loop. What happened?
https://lemmy.world/post/1290412
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.
Appreciate the info.
lemmy.world has never been stable, nor has lemmy
Production services are actually fuckin’ goddamn difficult, and I add another swear to this comment for every time I have to try reposting it.
Yep lemmy.world is live (stress) testing in production. It has its benefits, like when a set of patches were committed to vastly improve performance that was a big problem on a huge instance like lemmy.world but not on the smaller ones, and its downsides with all the random issues that pop up which happen when testing live in production.
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.
Different instances have different levels of stability
Blahaj has been pretty stable for me except during the recent attack
Beehaw has been kinda meh on stability
Lemmy.ml has been pretty stable when I’ve used it
Jerboa (the app I use to browse) has been hit or miss at times, but has been really stable since instances moved to 0.18.
Kbin has had no issues for me and hasn’t been attacked yet (or if it has been, dev Ernest apparently fought them off, probably barehanded too).
Kbin gives me an error whenever I updoot a post, but that’s about it.
@Silverseren With nothing but spare keycaps and toothpaste, no doubt
Lemmy.ml was overloaded half of the evenings before lemmy.world found the causes of performance issues (now solved in 0.18.1)
I’m just going to use accounts other than my one on lemmy.world for a bit while they sort out whatever’s going on.
@Rockfury@lemmy.world ITS A
LEMMY MOMENT
Getting logged out randomly and having to submit comments multiple times for them to post sure is fun. /s
Clean app data and cache, login again, fixed for me at least
That seemed like it worked for me but then it happened again eventually.
Getting the same thing. Found out I was unsubbed from the sub I was following.
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. :)
Ernest is running lemmy instance or you’re talking about kbin?
Yeah, kbin here.
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.
