I don’t understand why they don’t use the client side filter-variable in Lemmy UI. It has been available for a while now. It solves a whole bunch of problems. Summit implemented it a few versions ago and it works great. I can hide and unhide posts with the push of a button.
I use Summit and I don’t know the feature you’re referring to. Could you explain it?
I’ve used the instance name filter to block lemmy.world from my feed because it drowns out less popular/new comms, but it’s really annoying to have to go into the filter menu to add and delete the filter all the time because I don’t want it filtered permanently.
I don’t understand why they don’t use the client side filter-variable in Lemmy UI. It has been available for a while now. It solves a whole bunch of problems. Summit implemented it a few versions ago and it works great. I can hide and unhide posts with the push of a button.
I use Summit and I don’t know the feature you’re referring to. Could you explain it?
I’ve used the instance name filter to block lemmy.world from my feed because it drowns out less popular/new comms, but it’s really annoying to have to go into the filter menu to add and delete the filter all the time because I don’t want it filtered permanently.
You can click the eye on top of a feed to switch between seeing and hiding read posts.
The default web UI has that, in the feed.
I never saw that before because I never tried hiding read posts. That’s good to know, thank you!