Lemmy 0.19 Mandates 2FA Reset; F-Droid/Play Store Builds Confuse Users, Devs Warn of Compatibility Trap
The Lemmy 0.19 upgrade forced a mandatory reset for users, requiring the re-enabling of Two-Factor Authentication and logging out across all clients to ensure functionality.
The core conflict centers on client readiness. 'Shadow' argues waiting for apps is impractical, but 'avidamoeba' cautions against immediate updates, pointing out critical discrepancies: the F-Droid build signature differs from the Github and Play Store versions. Meanwhile, 'TheWaterGod' praised instance blocking but flagged that NSFW marking remains unreliable, citing issues in war reporting.
The weight of opinion suggests immediate caution is required. Users must juggle enjoying quality-of-life wins—like scaled sort lauded by 'Mereo'—against technical headaches. The fault line is clear: platform features are updating, but the client ecosystem lags, threatening a fragmented user experience.
Key Points
#1Mandatory Client Action Required After Update
Users must re-enable 2FA and log out/log back in for Lemmy 0.19 to function correctly.
#2Critical Client Version Incompatibility
'avidamoeba' exposed that F-Droid, Github, and Play Store builds use different signatures, preventing updates across sources.
#3Mixed Feelings on New Features
While 'Mereo' praised instance blocking and scaled sort, many found the visual 'gold highlight' on comments ugly and hard to read.
#4Technical Development Pace Debate
'Shadow' pushing for immediate use clashes with 'avidamoeba' advising a week-long delay for stable third-party app releases.
#5Persistent NSFW Tagging Flaws
'TheWaterGod' noted that even with improvements, the system fails to accurately flag all NSFW content, citing failures in Ukraine war reports.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.