Mark as read or Hide article

[imhariprakash]

Currently, articles reappear every time the page is refreshed, even after they have already been read. This makes it difficult to manage the feed and avoid repeated content.

It would be very helpful to have an option to:

• Mark an article as Read
• Hide / remove unwanted articles
• Persist this state (even via localStorage would be sufficient)

This would significantly improve usability, especially for users who check HackerTab frequently.

[medyo]

Yes, that's a good feature,

Would like to work on it @imhariprakash ?

[imhariprakash]

I’m new to the stack, but I’d love to take this up and give it a try.

[imhariprakash]

I’m planning to track read/rejected item IDs per source (using a lightweight log) to implement this feature. To avoid unbounded growth, the idea would be to periodically clear this data (for example, on a daily basis).

To do this, I’d like to better understand the backend API behavior. I noticed that the /engine/feeds endpoint (with source and tags) returns 25 items per request.

Does the API support any pagination-related parameters such as limit, offset, page to fetch additional items or control the count? Also, how is the feed distributed for a given source—does it refresh/rotate daily, or is it based on a rolling window (latest n items)?

If the feeds are rotated daily and older articles don’t reappear, clearing the per-source log daily should be sufficient.

[medyo]

Yes, that’s a good approach.

The /engine/feeds endpoint returns a fixed number of items (25 per request, with 50 as the maximum) and does not support pagination for now.

For each source, the feed is based on a rolling window of the most recent items. As new items come in, older ones may disappear from the feed.

To keep the implementation simple, we can use your log-based approach, but we’ll keep the data for longer than one day or limit it by a maximum size.