this post was submitted on 15 Dec 2023
176 points (98.9% liked)
Lemmy.ca's Main Community
2788 readers
1 users here now
Welcome to lemmy.ca's c/main!
Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.
Announcements can be found at https://lemmy.ca/c/meta
For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, lesson learned :/
I'll compile a list of apps and see how we can track which one are ready for any API breaking changes before we do the server update.
I'd just delay the update for a few days up to a week. That would give a chance for most maintained apps to release updates via their respective channels. Then I wouldn't have to care and check for specific apps.
The app developers were warned like a month ago that this would be a breaking change, they had lots of time to release patches and there's been a few large instances on the beta of 0.19 for well over a week.
IMHO It's not really sensible for us to go test the apps and then hold back on upgrading just because one of the dozen apps isn't compatible yet.
What's even worse is that the Jerboa developer is one of the Lemmy dev, he could litterally see this coming a mile away :/
But on the other hand he's at the mercy of Google making the update available whenever they feel like it.
It's why I wouldn't test at all. I'd just wait a bit. Or I'd update after Lemmy.world updates. 😅 Little extra work that way.
Most of the aps can't even distinguish between ~subscript~ and ~~strike-through~~