Sync read state with API providers

[kevinschweikert]

I've connected my Miniflux instance with Nom. Worked great, all feeds are there. But when i read an article it still shows as unread in Miniflux. Could we push the read state back to the API provider?

[guyfedwards]

Thanks for the issue @kevinschweikert.

The current backend implemntation for miniflux/freshrss is very naive and just sources feeds, nom then fetches the article separately.

We could add a more feature-ful implementation where essentially backends become another store and all writes to the local store, are also written to the backends, this would be a meaty refactor of backends but I'm not against it.

Thoughts:

• If we write read back to the backend, it feels bad to not also read the read state back, so the integration would need to be tighter and read/write from backend.
• We have tags in nom, and tags from miniflux, again there should be some alignment/synergy here.
• There is probably a feature-disparity between freshrss/miniflux (I don't use either so not sure)
• My concern is we start to get into UI client for miniflux/freshrss territory

[kevinschweikert]

Hey @guyfedwards,

i feel your concerns going full UI client for miniflux/freshrss and i can totally understand if this is not a direction you wan to go.

The reason for suggestion this feature was, that i expected it to work in both ways and had to find out, that the backend configuration is just for importing the feed urls. I would love to consume my RSS feeds from the terminal (you did a wonderful job with nom!) but keep them in sync when i read on my phone. That's why i am using Miniflux in the first place, to manage them in a central place.

So i personally would love to see a tighter integration!

[guyfedwards]

Yea I can see that, and definitely think this is something we could support. Are there other features you would like synced as well? Read/unread is the most obvious but maybe favourites are a thing as well in miniflux?