I have recently begun using the trainer, and I really like that it hides stories which contain keywords, that I’ve chosen.
But sometimes I like to check that the trainer hasn’t hidden anything I didn’t want to miss.
I click the “Show hidden stories” button. to show the hidden stories, but there is no way of actually hiding these stories again afterwards, without refreshing the view.
As you can see in my picture, no. 1 and 2 is the behavior before and after the button is clicked.
And I’ve made a mockup of how I’d like this feature to be improved. no. 3. being before showing the hidden stories and no. 4 being after.
Maybe “Filtered stories” is better than “Disliked stories”, now that I think about it.
Yup, this would be a nice addition. Maybe not so much because it’s needed, but because it just makes sense to have the option.
And yes, “Filtered stories” is better than “Disliked stories”, first thought when I saw the mockup.
Neither disliked nor filtered are clearer than hidden to me. But having the option to rehide stories is certainly something I’d like. It’s obviously something I had to cut in order to ship that back three years ago. I could revisit that again, although I’m not sure if it’s a simple fix.
I just thought that “hide hidden stories” would be a bit confusing. That’s why I think “Hide filtered stories” gets the message through.
Any update on this?
It’s quite annoying having to refresh the website, after taking a quick look at the stories, which were hidden.
Oh, right, I should turn that into a toggle. It’s probably not too much work. Ping me on this during the week if you want it to happen. Email wouldnt be a bad idea either: firstname.lastname@example.org.
Just gonna bump this thread again. I’m in no hurry, but would like to see this feature implemented at some point
Ok, here’s a ticket for this feature: https://github.com/samuelclay/NewsBlur/issues/823. Now it’ll get done eventually.
Thanks a lot.
Small question: Should we write tickets ourselves on github, Or do you prefer collecting issues through here, and creating the tickets yourself?
I prefer creating tickets on github. I use that to prioritize work. If users write tickets, I’ll close them if they are feature ideas that I am not yet committed to (even if low priority). If they are actual code issues like installing NewsBlur, I’m happy to help there.
Really, it comes down to the fact that users can do no wrong.
And no problem at all. Keep up the great work Samuel!