Bug Report

Switching accounts will clear the image cache. Perhaps this is intentional and if so, seems inefficient.

With community stacking disabled, if you turn on show page numbers, page 3 is skipped entirely. I’m kinda curious why since it’s so oddly specific. The other pages seem fine; just 3.

For this one and the previous issue, you need to close and reopen the app after enabling the applicable settings. Turning both community stacking and page numbers will result in bad page markings. Some pages are really short, others have more than one page marking.

On that note, I’m guessing community stacking just stacks posts one page at a time right now. Perhaps it’s not feasible to keep a running list and keep stacking as the feed expands but increasing the threshold to 2 or 3 pages would be better since the stacking seems to miss a few when I scroll All.

My block settings page won’t render and I get stuck on the loading screen. Is it just me? Also, blocking now doesn’t atuo-remove the post(s) from the feed.

Lastly, maybe we could get a Piefed Connect community now? The Lemmy side is at a pretty good place now with the performance and cache issues behind us.

EDIT: One more that I forgot. The sticky community sort is affecting and overriding the default post sorting. It should just affect feeds and not comments.

Device Information

  • App Version: 1.0.324 (324)
  • Platform: android
  • OS Version: BP4A.251205.006

Modified Settings

The following settings have been changed from defaults:

  • isNotificationEnabled: 1 (default: 0)
  • commentDividers: 0 (default: 1)
  • isCommentActionsReversed: true (default: false)
  • shouldAlwaysOpenInDefaultBrowser: true (default: false)
  • shouldDisplayTitleAbove: true (default: false)
  • alwaysShowInstance: true (default: false)
  • applyUserNotesGlobally: true (default: false)
  • isEdgetoEdge: false (default: true)
  • alwaysTrustDomains: true (default: false)
  • shouldUseHighRefresh: false (default: true)
  • shouldLimitCardImages: true (default: false)
  • commentTextStyle: bodySmall (default: bodyMedium)
  • postTitleTextStyle: titleSmall (default: titleMedium)
  • customColoursPreset: 2 (default: 0)
  • enableCommentNavigator: false (default: true)
  • isTopBarFixed: true (default: false)
  • showFullVotes: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldInstanceBlockIncludeUsers: false (default: true)
  • shouldHighlightNewComments: true (default: false)
  • isImageVerticalSwipeToClose: false (default: true)
  • shouldStackDuplicatePosts: true (default: false)
  • defaultRoute: /community?postListingType=All&hint=All (default: null)
  • defaultPostSort: New (default: Active)
  • defaultCommentSort: Top (default: Hot)
  • cardType: list (default: card)
  • swipeActionsComment: [upvote, upvote, downvote] (default: [upvote, save, reply])
  • postActions: [comment, save, share, none] (default: [comment, save, none, crosspost])
  • swipeActionsPost: [hide, none, none] (default: [upvote, save, hide])
  • shouldRemembercommentPosition: false (default: true)
  • shouldUseProfileBanner: true (default: false)
  • shouldResolveOpenGraph: true (default: false)
  • shouldDisplayCommunityBanner: false (default: true)
  • shouldForceBlackImageBackground: false (default: true)
  • stickySortSettings: true (default: false)
  • theme: amoled (default: system)
  • textSizeMultiplier: 0.875 (default: 1.0)
  • kuroM
    link
    fedilink
    arrow-up
    4
    ·
    10 days ago

    Thanks for the report and I will take a look at these in the next release. I released 325 on beta about ten minutes ago but I don’t think it would change any of these issues.

    Cheers!