this post was submitted on 19 Sep 2023
579 points (94.1% liked)
Sync for Lemmy
15088 readers
1 users here now
๐
Welcome to Sync for Lemmy!
Welcome to the official Sync for Lemmy community.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Community Rules
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Community Credits
Artwork and community banner by: @[email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, not really. This was JUST a problem for Jerboa. There were some other 3rd party apps available for Lemmy and they didn't suffer from the same problems. In fact, it wasn't even a technical limitation of Jerboa itself... if you had previously installed and configured Jerboa when the instance version and the jerboa version matched, and then upgraded your jerboa app when your instance didn't upgrade their version, it magically worked. The problem was when you installed Jerboa fresh and tried connecting it to a slightly outdated instance version - or if you wrecked yourself by clearing your jerboa cache/data folder without realizing that it would behave like it was starting fresh and break. The problem was solely in over-aggressive version checking during Jerboa startup....a total rookie mistake.
That's about the time that half of all Lemmy users suddenly learned about the availability of some competing apps that didn't have the same problems.
I'm talking about other version numbering issues that all of Lemmy experienced at that same time. While the one you spoke about was Jerboa specific, I experienced the other issues on the web as well as on Sync. As you pointed out, Jerboa is developed in parallel with Lemmy and it seems like these issues were a blind spot for the developers.