-
Notifications
You must be signed in to change notification settings - Fork 67
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to hide read posts by default #913
Comments
I think the first step to this is to add an option which syncs up to your Lemmy account settings. Lemmy already has a setting to allow hiding or showing read posts. This option wouldn't be as granular has being able to choose to hide posts in Subscriptions or on a community-basis, but that might be something to be explored in the future. |
@hjiangsu this feature seems to be broken with v0.19.0 instances. |
Just wondering, but did your instance recently upgrade to 0.19.0? If so, you may have to log out and log back in for things to work! There were authentication changes made behind the scenes so this might be what's causing the issues. Let me know if that fixes the issue or not. |
It seems like this may actually be on Lemmy's end with the 0.19.0 update: LemmyNet/lemmy#4290 |
Oh yes, I've logged out and logged back in to get back my subscribed communities after the instance has been updated to 0.19.0. I guess it's really on Lemmy's end then! |
Could you let me know if this is fixed? It seems like a fix was pushed in Lemmy 0.19.1. If it is fixed, I'll mark this issue as closed! |
I can indeed confirm that this has been fixed in 0.19.1 instances! |
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
An option to automatically hide read posts in subscriptions or per community.
Describe alternatives you've considered
Manually hiding all posts when the page is refreshed or app is reloaded.
Additional context
Issue might be encountered if a huge number of posts are already read.
The text was updated successfully, but these errors were encountered: