thunder-app/thunder

Auto-dismiss read posts

Closed this issue ยท 8 comments

Is Your Feature Request Related to a Problem?

When I have already read a bunch of posts in my feed, and then refresh the feed, I see all my read posts.

Feature Description

Option to automatically dismiss read posts after a reload

Alternative Solutions

No response

Additional Context

No response

You could possibly use the Lemmy feature for hiding read posts.

image

The nice thing about this feature is that it syncs to your Lemmy account and also applies to the web UI.

(That is unless I am misunderstanding what you're looking for. ๐Ÿ˜Š)

I always have that enabled, seems to be a bug then

Just to clarify, you should have "Show" "disabled" if you want to "hide" posts. (I'm assuming that's what you meant! ๐Ÿ˜Š)

Two questions:

  • Do your read posts appear in your feed on the web UI as well?
  • Do your read posts appear grayed out in Thunder?

Oh yeah that's what I meant. I don't use the web UI much, but I can't remember encountering the issue there. And yes, they appear grayed out in Thunder. To be honest, I kinda forgot that this even feature exists, since (at least for me) it never does what it's supposed to. Thanks for the quick reply and the effort to improve the app btw!

No problem, happy to help! If you get a chance, next time you see the issue, can you pull up the web UI (even if it's on mobile)? The list of posts in your feed should be identical (assuming you're using the same sort type). That setting is a server-side thing, so we're not doing anything in Thunder to filter out posts.

Thanks for the feedback!

After experimenting around a little with the web UI, it appears to be an issue on the server side.

After experimenting around a little with the web UI, it appears to be an issue on the server side.

Hmm, could you clarify this? It seems to be working on my end on lemmy.world. I have "Show Read Posts" disabled in the Account Settings

Sorry for not responding for 2.5 months, I probably overlooked it in my GitHub notifications. However the bug seems to be gone now, so I'm closing the issue.