Yes rollback had to happen. Everything went ok for a bit and then it went VERY slow. So the decision was made to roll back to 0.17.4 for now. We hate it just as much as you ;)
I’m not hating it at all. Stuff like this just happens. Lemmy (the software) as well as this instance was pretty much overrun by a stampede of new users while trying to make its first baby steps. What would you expect?
I just meant that we were also hoping to upgrade and be done with some of the issues that are really annoying, such as the endless scrolling on the frontpage and such. And we did some tests on a test-instance, talked some things over with the lemmy devs and everything looked good. And then we upgraded the live environment… And that didn’t go well :)
Everything was beautiful for a minute there.
I found the
UI 0.18.0 | BE 0.18.1-rc.1
combination to be awfully slow and buggy.Why not just update both Backend (BE) and Frontend (UI) to
0.18.0
and disable signups until0.18.1
is released? I mean,lemmy.world
really doesn’t suffer from not having enough users, right?deleted by creator
On the other hand it appears to me that
lemmy
(the software) isn’t quite ready to handle such a massive influx of new users. So what is better?- Ask for patience
- or have many,many people get (and possibly report) a far from optimal experience?
I’m pretty confident that in a few weeks or maybe months
lemmy
has matured enough to easily handle the amount of traffic it is currently struggling with quite a bit.Your comment raises an interesting question: How prepared is Lemmy (the software) to scale?
I’d say not that well. It’s still very young, and this is almost certainly a lot more users than the developers were originally expecting at this point in time.
Part of the motivation for them moving away from web sockets in the first place is because the bugs and inefficiencies with using websockets made it less efficient, increasing the amount of load when the instances got big.
Mass moderation and post sorting tools don’t exist yet, and there’s no automated moderation system, which is a must-have for big subreddits/communities.
If you were around for early Reddi that site was atrocious for blackouts and they even said they’d reached the limits of current technology about 10yrs ago until they finally switched from Postgres for the main site.
0.18.0 would have given us the same issues we experienced today. We tried everyhing on a test-instance before but once the live was upgraded it went from good to bad very fast. Json errors, 2FA issues and then the slowness.
This is kinda odd since
lemm.ml
is running0.18.0
on both BE and UI for quite a while now. Also I got the foillowing error message quite frequently and the UI was unresponsive until I refreshed the browser window. But maybe this was whileUI 0.18.0
was active withBE 0.17.4
. Looks like now eveyrthing is back to0.17.4
.Update: Looks like deleting all
lemmy.world
site data in my browser (chrome) and logging in again solved this issue.When do you expect to turn into the next u/spez. Are we talking years or months or weeks?
Are you a fan of Elon Musk?
Are you American?
Which political party do you support?
Do you have lop-sided eyes and invisible eye brows?
What are you on about and what does that have to do with the rollback? :)
I tried clearing my cache and logging out/back in again but my front page shows no posts. I can see them for a fraction of a second, but then everything disappears.Edit: I also keep getting this error on the bottom of the screen: SyntaxError: Unexpected token ‘Q’, “Query dese”… is not valid JSONEdit 2: I deleted the cookie for lemmy.world and that seems to have fixed it.
Thank you for the clarity. You are great 👍