In anticipation of Lemmy's upcoming 0.19 release, and to work out any final issues, we're going to deploy a test release on lemmy.ml within the next few days.
We're doing this testing on lemmy.ml only, so that we can encounter any issues before the release, and to make sure the upgrade process is smooth for other production servers.
Some of the following will happen during the process:
Lemmy.ml may experience some downtime for the upgrade to complete (ideally no more than an hour).
If anything goes wrong, we may have to restore from a database backup, meaning content made in between backups may be lost.
If all goes well, we'll have an official announcement for the release after this testing period.
I apologize for the difficulties this might cause. At most this will be a week of hair-pulling, but its vital that we catch any issues before telling other servers to upgrade.
Thanks everyone for the server and service. It's appreciated. If I wasn't broke and jobless at the moment, I'd be happy to kick over some monthly money on Patreon or Kofi or whatever people are using these days.
This is good to hear! Have you considered releasing more often with smaller sets of changes, for future releases? It seems like this will be quite the upgrade.
Yep, we'd def prefer to do smaller releases, and we'll try to make them more frequent and smaller in the future. The main reason this one was so delayed, is because of the large number of breaking changes, esp. w/ respect to authentication.
The update has broken a bunch of things for me..
On my desktop using firefox, I cannot get images to display & everything is slow to load. On my android phone, boost was showing me a ton of stuff that I do not follow & wasn't showing me any info about my profile (profile tab would not load or something). Boost eventually logged me out & I have been unable to log back in....
Images were temporarily broken due to authentication problems, but thats fixed now. If you encounter problems in apps, please them to the developers so they can fix them.
I have experienced the same login bug on the Mlem app as well. One of my devices stayed logged in and is working perfectly; my other device logged me out of lemmy.ml and I have not been able to log back in on that device.
Honestly, I have some problems with this update (and some things I'm super happy about too of course), I hope my feedback is seen so the problems can be made aware:
I'm not a fan of new comments having yellow, the contrast is poor at least on darkly-compact and it just looks weird and out of place. I'd suggest maybe making them a slightly lighter or darker shade of the existing color to make them stand out, not an entirely different color.
It seems the main page/posts pagination uses pageCursor instead of page number now, whereas profiles still use page number. Using pageCursor is an SEO downgrade and usability downgrade, it's a weird decision IMO if that was intentional and not a bug.
I think I might have run into a bug, Lemmy no longer seems to save my upvotes or something. When I upvote some posts on the main page/posts list, even if I wait a few seconds, or 10 seconds or even 30 seconds, when I refresh my upvotes are gone. This one seems fixed now? Nevermind, it's broken again, very weird.
With "Top Day" sorting, there used to be multiple pages of posts, now sometimes I don't even get a full page of posts: https://i.imgur.com/4LiZzJG.png (it looks like it's showing posts from only one community, I have it set to subscribed communities but I'm literally subscribed to like 50 different communities) but other times I get one full page of posts plus multiple other posts which is how it always behaved before 0.19. Since it seems to be inconsistent, I'm thinking that's a bug.
I would probably suggest on holding off on releasing 0.19 for now, it does seem like a really large release so it might be better to make sure it's fully polished and ready to go.
I'm super glad upvoting comments doesn't discard the comment you're writing, that's a huge improvement. I also see import/export settings, that's super awesome, I absolutely love features like this!
Thank you for your hard work, Lemmy is such a cool platform.
Awesome, glad to hear those issues are aware of! Best of luck with fixing them, it does sound like a challenging bug.
For the new comments having yellow being poor contrast, is that something that could still be fixed? It seems to be really poor contrast and hard on the eyes, a couple of my friends noticed this too.
For the pageCursor not using page number, is that intentional or could it be fixed to use page number again?
I was just wondering: Instead of testing these potentially disruptive changes on the main website, why wouldn't you make some testing instances where people can try everything out, like voyager, enterprise, and ds9 were back in the day?
I don’t think this is a bad suggestion, but it’s worth noting that lemmy.ml is explicitly intended not to be the “main” Lemmy, or even a major one: What is lemmy.ml?
Yep, I've been enraged by this decision from day one. This is depressingly amateur. Let people join, let other developers make very cool apps, and then introduce a deeply breaking change in a minor version, and deploy it on the most active instance, with mere days of warning. Or "How to destroy all the progress made by Lemmy, in one small change".
I get it if the devs and admins of Lemmy.ml are paying too much out of their own pocket, and if they want users to literally go away, to mitigate that cost.
But doing it in such an in such an insidious, demoralizing way, as opposed to being transparent with the costs and announcing (drastic) measures to mitigate that cost, is literally destroying most of the progress made so far, and driving most users back to reddit.
As of today, the list of most active servers of the fediverse has only one Lemmy server (Lemmy.world), in ninth position, and that is the only Lemmy server in that list, over four pages... The Lemmy instances used to be in the middle of the first first 10 instances, with Lemmy.ml leading the way.
Now, I guess the devs didn't want to take those drastic measures, and tell people to they would be closing down their accounts, ordered by creation date, until the costs become bearable again. Because that would mean "admitting the Lemmy.ml experiment to show the world that people are, when given the opportunity, rising to the challenge, and putting in the effort, in true communist fashion, is actually a failure". People aren't ready for communism. Communism requires education, intelligence, and empathy/compassion. Our western societies are fostering the opposite traits. When we become educated, intelligent, and empathic or compassionate, it is in spite of our societies, not thanks to them.
Now, a few people opened instances, but it wasn't enough, and fast enough, when the "reddit migration" happened, to absorb the insane influx of users to Lemmy.ml.
So I guess it is what it is, but it's still sad and depressing...
How much longer will it be before I can finally log in and use boost or liftoff. Is there a timeline for a fix? Both have been broken since the update.
I think it would be good practice, that verifying app support should take a front seat in the future before upgrading.
The way it is currently handled, is not a good practice to retain users, but rather drive them away.
I appreciate that you going through this test period. I hope it all goes smoothly and that at least a few hairs remain on your heads by the end of this week. Good luck!
The 2FA on Lemmy was broken in the sense that if you turned it on, it didn't test you to enter the correct token and then properly activate itself. Thus, it led to many people being locked out of their accounts(unless they were logged in somewhere else as well, in which case they could turn off 2FA). This led to the announcement that 2FA will be reset for users so that incorrectly logged out users can get their access back.
If you use apps, you can't even relogin. Expect this if you're using app like boost, sync etc. However you are okay if you're using Voyager because it is browser-based.
I've been having these issues at lemmy.sdf.org when they update to 0.19, for about two weeks now I think. I use Sync and the dev are aware of the issue. But there's still no fix even though the dev is very quick in fixing bugs before. So I think, this is a major issue for app and it will take quite a while before we will see any fix.
Nope, I only have a lemmy.ml account, and I only use librewolf on the desktop...
I had that issue of having to re-login, and then every now and then when I do reload, it posts not on my subscribed communities as if I were not logged in, although I'm logged in, but on a subsequent reload, then only my subscribed communities posts show up. I haven't had to re-login again, just after the upgrade, and then the other minor annoyance is that, but a subsequent reload is enough...
Screw community names, I want instance agnostic URLs for posts and comments.
Right now lemmy.ml/comment/123456 and lemmy.ml/comment/123456 are two different comments, and there is no simple way to find one comment on another instance (so you can interact with it from your logged in account). What we should have is lemmy.ml/comment/[email protected] to point to a comment made on another instance, then you can just change the instance name after the @ to find the comment (or post) on any other instance.
Comment IDs are not unique between instances so you simply cannot change just the part after the @ to link to the same comment but accessing it from another instance.
You can always take the comment’s full URL and put in in the search field of your instance, this will show that particular comment in your instance so you can interact with it from there.
I've saw a weird phenomenon where someone else user was written in place of mine for a second when I opened the web page. I was not connected, one a PC using Firefox.
Could it be related ? Is this the right place to signal it ?
One problem is that a few communities, while they do show up in my subscriptions list, do not indicate that I am subscribed to them when I am on the community page (for example, [email protected] is one of those communities where I noticed that issue, it mostly fluctuates between me being subscribed to the community or not). If it needs to be marked as an issue on GitHub, you can let me know.
Hearing that this update was supposed to make borking your account harder to do when setting it up, I enabled it. Put the secret in my authenticator app, got my six digit code, and away I went.
Now, a few days later, having changed nothing on my end, Lemmy.ml won't accept my TOTP code. My session token on desktop is expired so I can't remove it now.
Currently my only lifeline to this account is my logged in session in Voyager, which, as far as I can tell, cannot access the TOTP setting. (Or any profile setting, for that matter... am I just stupid?)
No email to recover from, either. That's on me, I guess. Ugh.
Any other type_ works. This one used to return only a users Subscribed communities but it just returns an empty array {"communities":[]}. When you load it up in a browser it works. I'm driving myself crazy
Boost for Lemmy (v1.0.3 Nov 16, 2023) seems to be having issues with this 0.19 release.
While using Boost, I stayed signed in, but my feed while set to Subscribed was showing posts not under my subscriptions. I blocked most memes communities for example yet they all showed back up, filtering by Subscribed or All they appear like identical feeds. After I signed out, to see if it made a difference, I am unable to sign back in. I'm posting this from Firefox/the web browser instead of the Boost app.
Is it normal that opening comments now completely refreshes the page instead of automatically loading the page semi-dynamically? if I click the comments button on beehaw the whole page doesn't have to reload, and it's actually faster. This seems like an annoying regression, is there a technical advantage to this?
edit: on further analysis, it doesn't do a full page load when you go to your username > profile
or when you click on comments from the link, so, I think this is actually a bug.
Is anyone else unable to see a list of their own posts in their profile area? For example, I have several posts in /c/[email protected] that aren't showing up in my profile.
Has anyone experienced trouble logging in through Jerboa app? Jerboa crashes every time I try to log into this instance, but other instances log in fine.
Creators of Lemmy, owners of this instance, and creators of the Jerboa app are all the same people. As I understand it, Jerboa won't be getting an update until they're happy with the stability of the update to Lemmy itself. Lemmy is getting all the focus first. Also, no sense in pushing a client update for a server update that itself is not finished.
Getting really annoyed at that error toast in Jerboa, though, not gonna lie. And not being able to post on mobile. At least I can still read posts and comments, though. Hopefully the patch will release soon.
Yes, the exact same was happening for me. Jerboa would crash and android would show me the notification "this app has a bug" whenever I tried to login. Now using Eternity for Lemmy and that is working smoothly.
The site feels faster, the notifications are more reactive, and moderator view is a godsend.
As for now, the only new bug is fairly minor, markup-related. Examples here and here, screenshot:
Before the update, "há" "a" and "haver" would use a plain highlight colour (they were using the `code` markup); "dog**'s**" and "cat**'s**" had bold face.
EDIT: all good, I worked it out, I found some other api docs.
Is the ModeratorView listing type in this release? If so what feed view is it available in? I can't see it in the lemmy.ml webUI at the moment, nor in the API docs, but the code is merged.
The logout is normal, it's because there was an issue with the way logins worked before, that shouldn't happen on future releases, but that is to be expected this release.
There was a one-time sign-out with this release due to an issue with logins, see if the issue is still occurring for you, if it is, it's likely a browser-side configuration issue.
Its cause lemmy.ml doesnt show up on some of the apps now. I have to use my browser to use my account when i was using liftoff and boost before. Growing pains are gonna pain, but they are necessary.