this post was submitted on 12 Mar 2026
0 points (NaN% liked)

Connect for Lemmy App

3814 readers
1 users here now

A community for the mobile app Connect for browsing Lemmy and Piefed.

Links

founded 2 years ago
MODERATORS
 

Bug Report

Describe the issue: I have the setting turned on to hide posts that I've read and I also have the setting turned on that marks a post as read once you scroll past it. It seems like I continue to see certain popular posts though. Sometimes I will see a post pop back up multiple times over the course of a day. Has anyone else experienced this? Is this a bug or am I misunderstanding the limit or intention of these settings?

I put the bug report stuff on this for if it's actually a bug.


Device Information

  • App Version: 1.0.421 (421)
  • Platform: android
  • OS Version: UP1A.231105.001.B2

Modified Settings

The following settings have been changed from defaults:

  • shouldDisplayTitleAbove: true (default: false)
  • alwaysShowInstance: true (default: false)
  • shouldMarkPostsOnScroll: true (default: false)
  • shouldHideReadPosts: true (default: false)
  • imageDomainRewrites: {} (default: {})
top 3 comments
sorted by: hot top controversial new old
[–] sirxdaemon@lemmy.ca 0 points 2 months ago* (last edited 2 months ago) (1 children)

Yeah, it's a current bug. The feature was working before and I think it's an easy fix so it should be back to normal in the next update or two.~~

EDIT: Scratch that, it seems to be working fine. I'll have to check this out in more detail.

EDIT2: Are you possibly trying to hide a sticky post? Because currently you can hide it but then it comes right when you refresh the feed.

EDIT 3: Ah, so if you hide any post, it will hide it but it doesn't seem to be saved because once you refresh the feed, the post that should be hidden is back.

[–] you_are_dust@lemmy.world 0 points 2 months ago

Yea, that sounds right. Feed refreshes seemed to be when I'd see things again.

[–] kuro_neko@lemmy.ca 0 points 2 months ago

Hi, thanks for the report and this will be fixed in the next release (aiming for tonight). Cheers!