Hi, thank you and congratulations for the work on this great app
I have a small suggestion: add the possibility of setting, per stream, a defined time after which the publications of this feed are marked as read automatically. To lighten the number of unread, which we can never read. For example, I am subscribed to https://ladecadanse.darksite.ch/rss.php?Type=evenements_auj which is a cultural agenda of all the cultural events of the day in Geneva. I would like publications to be marked as read every day, because I don’t need to know what the events of the days before were if I didn’t go to see the feed. I could also decide that every week, the publications of such a stream are automatically marked as read, because if I did not read them in the week I would never read them. This could be settled by a long press on the flow in question, which would then make it possible to settle the time after which this flow must be marked as read.
It seems to me that this would make the consultation of NetNewsWire a little more “zen”. What do you think of the idea?
Yes, this is a feature proposal that I would appreciate. I would like to be able to help you do this, but I do not have the required skills. (And sorry if my question is not clear, my English is very limited… text translated with the help of my phone)
I think this is indeed interesting, but would the thought be to expire based on time elapsed since the posting date or time elapsed since it was retrieved by NNN? The reason I ask is because I see a number of feeds where the posted date is sometime in the past. So in the example of a feed of calendar events, if the post is dated August 1 but is downloaded by NNN on August 2 and is announcing an event that happens on August 3, I could see a number of interesting conflicting scenarios that might prevent you from ever seeing the post at all? I guess it might be simpler to just have a setting that says every day at time X mark all posts in this feed as read no matter what, but then you run the risk of missing something that had only been in the feed for like 10 minutes.
The posting date makes more sense to me. Whoever wrote the post might have included information that would date after a certain time the post was published. They would have no idea when their post would be retrieved by NNW or any other feed reader.
But my hunch, though, is that the main use case for this will be for people who just want to keep their unread counts from going up and up. This will be a nice convenience for them.
(I’m thinking of making it a per-account setting, even.)
I do think it’s more useful to customise the expiry date for each feed, as some feeds are very active whilst others are much less so. For example, if you’re subscribed to a blog that posts once or twice a month, you can leave it unread for a long time, or even indefinitely. In the case of the Geneva events calendar I mentioned as an example, they publish two feeds: one on the date the events are published (which helps you plan future outings) and another on the day of the event (what’s on tonight?), which results in a lot of posts every day (over 100 posts on some days, per feed). In this case, deleting the feed 24 hours after it’s published seems ideal to me. Or perhaps the option to choose, per feed, the number of recent posts you want to leave unread? (For example, 100 or more for the events calendar, and 5 for a less active blog).
