New
- Support for Lemmy 0.19
- Lots and lots of refactoring cleaning up technical debt
- Added “Account settings” to replace “Lemmy Settings”
- This new section syncs up with your Lemmy account
- A few things will need updating such as your nsfw setting and sort
Changes
- Any action that fail now alerts the user via notification
- Show / hide NSFW has been moved to Settings > Account settings (this now respects your account choice)
- Sort has been moved to Settings > Account settings (this also now respects your account choice)
- Removed “mark posts as read” and “remember across devices” as Lemmy does this automatically
Github issues closed
- Tasker Integration: Action Configuration Broken & No Post Syncing #350
- User domain not shown in posts for accounts with a custom name #118
- Portrait 2 columns layout bug #11
- Unsubscribe action fails silently #151
- S4L doesn’t expose Bot account preferences #173
- Show NSFW content doesn’t sync with Hide NSFW Posts #170
- Show scores doesn’t sync with account setting #171
- Disabling “mark posts as read” does not work #356
- Show Read Posts not synced with Hide Read #174
- Default sort settings not shared with web app #163
- Show Profile Pictures doesn’t sync with Show Avatars #172
- S4L doesn’t pull/ignores web settings #70
- Crash when Biometric account lock is enabled #110
Other fixes
- Fixed a crash when searching within messages
- Fixed a crash in the in-built webview
- Fixed a crash when sharing posts
- Added a fix for HTML chars in the summarizer
Updates
- androidx.annotation:annotation > 1.7.0
- com.android.tools.build:gradle > 8.2.0-beta04
- com.google.gms:google-services > 4.4.0
- androidx.core:core-ktx > 1.12.0
Well that came out of left field
Lemmy 0.19 has a breaking change for it’s API. Can tell with the tech debt LJ has been sitting on this for a while waiting for that to go. This is definitely one of the longer release cycles for Lemmy
I had been expecting this.
Lemmy itself is still a work in progress and the new version apparently makes some major changes from the current version.
Sync is currently in a usable stable state so instead of squashing bugs in the current Sync version it was a better use of their dev time to work on a build for 0.19.