Display settings before subscription finished OR apply filter on an already added feed

[antivirtel]

I have a problem: if I'm using the subscribe function from the subscribe URL, it will download the contents instantly in case of popular feeds. The problem is, that I need eg. 10% of that feed, and after that instant download, the Filter setting will not apply, so I couldn't filter out the irrelevant entries.

So I'm suggesting to have a thing like this:

• display the settings before subscribing OR
• place a button after the Filter setting, to "Apply filter now"

Thank you!

[antivirtel]

Sorry, a bit off here... Maybe my expression is wrong, but I'm using this:

not (title.contains('bsd') or title.contains('firefox'))

on this feed: http://feeds.feedburner.com/HUP , and today I got this entry: http://hup.hu/cikkek/20150517/folytatodik_a_cd_mizeria_az_openbsd-nel - which clearly contains "bsd" in its title...

Is my expression wrong? I don't want to receive anything about bsd and firefox for example...

[Athou]

Indeed it should have been marked as read. I'll have a look.

And as your first question, i'm not sure it's that easy, I'll have to see what can be done.

[antivirtel]

Anything new about this? It doesn't seem to be a big request.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[antivirtel]

Anything new about this? It doesn't seem to be a big request to apply the filter immediately.

[Athou]

Currently, the filter is evaluated when a new entry in the feed is detected by commafeed.

What you propose would require commafeed to load all entries of the feed you're subscribing to, including their content, evaluate the filter on each of those entries and inserting a "read" status if the filter did not match the filter.

That seems like a very heavy operation, a feed could have thousands of entries :/

[Jorengarenar]

QuiteRSS has such feature: normally filter applies only to new entities, but when you click a button, it applies to all of them.
Since there's a worry about performance, it could be locked behind an option in server configuration.