Request for Unread and Saved Item IDs Like Fever API

[AiraNadih]

• [x] I have read this document: https://miniflux.app/opinionated.html#feature-request

Here's the Fever API's unread and saved item IDs:

## Sync

The `unread_item_ids` and `saved_item_ids` arguments can be used to keep your local cache synced with the remote Fever installation.

---
http://yourdomain.com/fever/?api&unread_item_ids
---

A request with the `unread_item_ids` argument will return one additional member:

-   `unread_item_ids` (string/comma-separated list of positive integers)
    

---
http://yourdomain.com/fever/?api&saved_item_ids
---

A request with the `saved_item_ids` argument will return one additional member:

-   `saved_item_ids` (string/comma-separated list of positive integers)

One of these members will be returned as appropriate when marking an item as read, unread, saved, or unsaved and when marking a feed or group as read.

Because groups and feeds will be limited in number compared to items, they should be synced by comparing an array of locally cached feed or group ids to an array of feed or group ids returned by their respective API request.

This feature can reduce the number of requests and resource consumption while synchronizing between the client and server, improving synchronization efficiency.

[fguillot]

That already exist in Miniflux's Fever API. Can you clarify your feature request?

https://github.com/miniflux/v2/blob/5de0714256e7b5ab5018842b4dea43cc9deba6c6/internal/fever/handler.go#L45-L48

[AiraNadih]

That already exist in Miniflux's Fever API. Can you clarify your feature request?

https://github.com/miniflux/v2/blob/5de0714256e7b5ab5018842b4dea43cc9deba6c6/internal/fever/handler.go#L45-L48

Thank you for your response. I would like to clarify my feature request. While I am aware of the existing functionality in Miniflux's Fever API, my request is specifically for similar endpoints to be available in the main Miniflux API, not just within the built-in Fever API.

The main reason for this request is that the Fever API is essentially a read-only interface, which limits its utility for certain applications. In the context of general RSS readers, typically only one API can be used to interact with Miniflux at a time. Therefore, having these endpoints (for unread and saved item IDs) directly in the main Miniflux API would be more beneficial. It would allow for a more versatile and comprehensive interaction between Miniflux and various RSS readers, going beyond the read-only capabilities of the Fever API.

This feature would significantly enhance synchronization efficiency and user experience for those relying on standard RSS readers for content management and consumption.

Looking forward to hearing your thoughts on this.