Thank you for the transparancy!
Lemmy.World Announcements
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news π
Outages π₯
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (PGP Supported)
Donations π
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
I love post like this, another reason of why this instance is so good
Both Dessalines and Nutomic have been working their butts off to get 0.18.x ready for the Reddit API changes. Huge hopes they can pull through!
Dessalines:
Nutomic:
Yeah they've been hard at work all month. But it's also okay if things aren't ready in time. Most of the people who matter are already here.
Maybe we will blow up soon, maybe later, but the quality of content here is sufficient to drive growth regardless of whether or not we get the prophesized huge migrations from reddit
is that users canβt login anymore
Ouch, that's bad :(
Thank you for your work, as always :)
I mean thatβs a Tuesday on Reddit lmao.
As any engineer who does ops can tell you - you did the right thing - the solution is always to roll back, never force a roll forward, ever.
We should totally do pre and post update parties though. Even if the update fails we can have an excuse for drinks and a fun thread.
Just curious, why are we updating now instead of waiting for the proper 0.18.1 release?
Reasons I can think of:
-
The official Android client for lemmy, Jerboa, only supports 0.18 and later, unless users download older version from github and sideload manually.
-
Sorting is broken pre 0.18, new posts keeps flowing in.
-
Performance improvement by removing web socket from lemmy. (which fixes 2, which is why 1. happens)
Federation is completely borked with .18 servers. Its very difficult for us to interact with https://lemmy.ca in any way: subscribing, upvoting, comments, posting... its all bugged.
Its maybe not that big a deal because Lemmy.world "has the most users", so in some regards its https://lemmy.ca's loss but... we need to restore reliable federation... especially before the July 1st rush IMO.
The .17 to .18 upgrade is basically a soft-defederation event, because of whatever this bug is between the two versions.
Because of a few things, really anoying bugs and the Jerboa app not working properly with older versions
I suspect there will be a large influx of new users in two days, and that having Jerboa not working on .world might cause a few issues
For example the frontpage is no longer being constantly filled with random posts when you set the filter to "active" or "top day".
UI: 0.18.0 BE: 0.18.1-rc.1 π
seems to be working for me, I was already logged on
appreciate the transparency. how are things looking in the back in lemmy.world (server wise)? will we get to a point where it wont require complete rollbacks on the state when a botched update gets rolled out?
Oh. Good luck with the next try!
Suddenly my Jerboa won't change from local and I can't change the sort. Not sure if this is related, but it was working fine yesterday after I updated the app. But no longer this morning.
Thanks for the transparency. Maybe itβs a good idea to have a test instance and some test cases/validation done there before updating the main instance. This is a regular process in any software/tech company/stack.
Testing should never be done directly on the prod instance.
i think they tested it which worked fine, but it is totally different when there are users online
Correct there was a test instance and that worked fine but once the live instance was upgraded everything became very slow. Can't really emulate that kind of load
I am glad I didn't write my last post during the upgrade process.
Maybe next time, give a warning, or maintenance notice.
Thanks for trying though.
Jerboa is almost unusable for me at the moment. A lot of crashes, pages not loading, messages not sending etc. But I know that's inevitable at times. Restarting my phone seemed to make it worse. But I know you guys are on it! π
Damn, Im glad you tried, and thanks for the update! I just really want the front page fixed without changing to page 0 lol. That and the 3/6/12 hour filter option.
Keep us updated. Im bouncing back and forth between LW, KBIN, and .ml for now though
any recommendations on other instances I should try outside the lemmy-verse and kbin-verse?
@[email protected] just wondering if you have considered setting up a second, beta, instance of lemmy.world open to the public?
With all the performance issues with 0.18.1, it's highlighted that there needs to be a way to stress test these updates before applying them to the main instance.
Yes, considering that. But we'll need people to use that when we will do testing...
Good luck! May the software gods bless you with a functioning website with minimal bugs!
I'm so new, I'm a baby, I have no idea what I'm doing. I did just create my account, I tried using the app but it wouldn't let me. Saying server version too low. I'm sorry for my ignorance, but is this what that means? And this means we can't use the app yet right?
Also, thank you for all of this. I will be here for it all, I'm staying forever! I already love this so much more than anything else π₯°
Running one of the largest and most vibrant Lemmy instances certainly makes this deployment a great test case for the devs and the system overall. @[email protected] this community really appreciates you!
Linux/Firefox After upgrade many things didn't work, but they continued not to work after rollback.
Turns out I needed to clear the cache, then everything worked fine again.
Thanks for the info. You're doing a great job!
PSA: If you've been using lemmy.world during the upgrades and rollbacks your browser might've cashed some stuff that quickly got out of date. If you have problems (especially JSON errors), try doing a hard refresh (usually Ctrl + F5) on the site. It might log you out.