"Add filter" button in the toolbar

[hirnsushi]

I would love a toolbar button in the article view to quickly add a new filter.

When I realize I want to filter articles like the one I'm reading, I currently have to leave article view, remember the headline, go into settings, and add a filter.
Having a button that opens a dialog prefilled with the headline, that I can just quickly modify and save as a new filter, would make this process so much easier.

[jocmp]

Tracking via #1531.

@hirnsushi, just to confirm, are you still using/referring to the filtering for local feeds?

[hirnsushi]

I should have clarified that, good point 🙂
Currently I'm still using local feeds but I plan to move to Miniflux at some point.

I had just assumed that there would be API endpoints to add/remove filters, but the Google Reader API compatible services only seem to support setting subscription-ordering, and I couldn't find anything in the feedbin-api reference either.
The only one that seems to support it is Miniflux, but only via the native REST API, which Capyreader isn't using.

Hmm, that complicates things, I'm inclined to drop this feature request, thoughts 🤔

[jocmp]

Miniflux is great! I've been wanting to add native support for a while, it just takes time to implement - though it would benefit a wider audience.

[DaLiV]

i see that more as next:
currently local filter already working - so here can simple change/extend to regex filter rules + add possibility save them "named".

user enters "coffee" + checkbox [case insensitive] rule and save/edit as "coffee"
even here "advanced user" can enter "(coff|t)ee" + checkbox [case insensitive] and save/edit as "drinks"
IT-People - they surely can then make more advanced and complex regexes by hand like "/(word|excel).*(critical|rce)/i", to filter even more exactly what they want "MSO-Security"

here also possible converter like from "word list" into regex for non-it ( as that will be much bigger task - that can be added afterwards on top of alredy working regex-es)

• any api is not best way as "limiting" for specific services only. locally fetched are most universal