Update: appears fixed in 1.0.434 released today.

Bug Report

Describe the issue: Hi, this is just a bug I wanted to share. A very strange issue has started I think after the beta update yesterday. (1.0.431, June 2, 2026)

In any view (Hot, New, Active, etc), the post list will load as normal, but after scrolling down past about 10-15 posts, will update and rebuild, seemingly finding additional posts and re-sorting them (think of an email sync, where emails in your inbox start appearing and re-sorting themselves). This goes on for a few seconds, completely destroying the selected sort order.

E.g., if you select New, it will at first appear correctly, but then after scrolling a few seconds a bunch of other posts will appear in dynamic updates, eventually leaving you with a jumble of posts not at all in New order.

I can record a video of this happening if it's confusing, but I'm not sure how else to explain it. Happy to provide any other information.

Steps to reproduce:

1. Open any feed view.
2. Scroll past 10-15 posts.

---

Device Information

• App Version: 1.0.431 (431)

• Platform: android

• OS Version: BP1A.250505.005.B1

• Migration: n/a (attempts: 0)

Modified Settings

The following settings have been changed from defaults:

• shouldLimitCardImages: true (default: false)
• defaultRoute: /community?postCommonListingType=Subscribed&hint=Frontpage (default: null)
• defaultPostSort: Hot (default: Active)
• applyNsfwInCommunities: false (default: true)
• cardType: list (default: card)
• swipeActionsComment: [upvote, upvote, reply] (default: [upvote, save, reply])
• postActions: [comment, save, none, none] (default: [comment, save, none, crosspost])
• swipeActionsPost: [upvote, upvote, save] (default: [upvote, save, hide])
• shouldLoadAllComments: true (default: false)
• imageDomainRewrites: {} (default: {})

I have a 56 TB local Unraid NAS that is parity protected against single drive failure, and while I think a single drive failing and being parity recovered covers data loss 95% of the time, I'm always concerned about two drives failing or a site-/system-wide disaster that takes out the whole NAS.

For other larger local hosters who are smarter and more prepared, what do you do? Do you sync it off site? How do you deal with cost and bandwidth needs if so? What other backup strategies do you use?

(Sorry if this standard scenario has been discussed - searching didn't turn up anything.)