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.
Voyager is heavy on memory, it’s killed by the system half of the times you want to use the browser for a minute. And doesn’t remember where you were.
Although it actually doesn’t mark posts as read, afaik without regard to the profile setting. Because it hides the posts instead. So they should probably be visible in search.
The setting to hide seen posts also hides them from search results.
What. Why. That makes no sense.
Hey you wanted to hide so we hid it. Forever.
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!
Yeah, I make good use of the Hidden Posts section in the profile page on Voyager, every time the feed refreshes for no good reason.
Voyager is heavy on memory, it’s killed by the system half of the times you want to use the browser for a minute. And doesn’t remember where you were.
Although it actually doesn’t mark posts as read, afaik without regard to the profile setting. Because it hides the posts instead. So they should probably be visible in search.