Feature Request: ability to ignore read/unread count and use it as a continous flow reader.

[leorac]

It would be great, since the inspiration is just lobster or hackernews, to have the possibility to ignore or hide the possibility to have read/unread news, and consequently have a unique feed in which the elements continue to flow, only having to deal with opening those that interest you most. Another possibility could be to do as freshRss and have the option to do "mark as read at receiving", so the elements are always set as "read". In this way you could create your own feed with your own sources, similar to hackernews or lobster.

[unwaivering]

.Please no!!!! There are plenty of others that do this.

[leorac]

.Please no!!!! There are plenty of others that do this.

please tell me at least one, because I can't find any of that!

[unwaivering]

As far as unread count, I thought it was an old-fashioned thing. Also as far as as you say "continuous flow" which is also called the river of news format, doesn't Feedly do that? In other words, make the RSS reader look like Twitter/Reddit/HN, which I really don't like but that's neither here nor there. I'm pretty sure newsblur does that as well, but I haven't been able to test so I can't be 100% sure of that.

[leorac]

No, you're wrong. When i'm talking about the continuous flow i don't mean to change the layout format. The layout should remain the same, but you don't have to check as read all the news. That's when the possibility to not differenciate the read from the unread come in place.

[unwaivering]

I never do because I have almost 400000 unread items. I read what I'm interested in reading, then I'm done. I do mark feeds as read when I'm done usually, so that they start over.

[patrickpichler]

@If actually just want to hide the unread counter you could use a somewhat fancy css hack like

.page-header > h1 {
  visibility: hidden;
}

.page-header > h1::after {
  content: "Unread";
  visibility: visible;
  display: inline;
  float: left;
}

.unread-counter-wrapper {
  display: none; 
}

This will get rid of the number next to Unread like

Edit: One downside is that all headers will get replaced...

[upward4]

@leorac what about just hiding unread counts? Would it be enough for your use case? Because that would be solvable with little changes in the HTML, i.e. by wrapping unread counts (including the parentheses) in <span> elements and applying custom CSS rules in Miniflux settings. This basically what @patrickpichler suggested, but without being an half-functional workaround.

I do like the idea of being able to at least hide unread counts, as they can quickly become overwhelming and of little use when the number of items approaches hundreds or even thousands.

I don't think hiding the read/unread functionality altogether is something that @fguillot would approve, based on the project's philosophy.

What do you @fguillot think of my proposal?

[unwaivering]

Maybe there should be a setting to hide unread counts, since so many people want that for some strange reason. You don't absolutely have to read all the feeds you follow at any given time. No one is forcing you to do that, including any unread counter. It's just there for data purposes. To the contrary, I usually don't start cleaning out feeds until there are at least 100000 items. This way, I have a decent archive.