Unread list forces exactly 400 items after Refresh (filling quota with old items), ignoring "Mark as Read". #12

New issue

Closed

opened 2026-03-17 21:23:30 -07:00 by serrebi · 0 comments

serrebi commented

2026-03-17 21:23:30 -07:00

Owner

I have observed a consistent behavior suggesting a hardcoded limit or buffer issue. After marking all as read and refreshing (F5), the application repopulates the "Unread" list to match exactly 400 items total.
The Behavior (Quota filling):
The application seems to prioritize filling the list to 400 items over respecting the "Read" status.
•
The total count is always 400.
•
It combines Newly arrived items and Resurrected old items.
•
Example: If there are 2 brand new items, the app resurrects 398 old items (dating back to e.g., Jan 22nd) to reach the count of 400.
Hypothesis: This suggests a logic error where a LIMIT 400 (or buffer size) is applied before correctly filtering out the locally "Marked as read" items during the fetch/refresh process. The app effectively says: "Show me the last 400 items from the feed," ignoring that I just marked them as read locally.
Steps to reproduce:
1.
Menu -> File -> Mark all items as read. (List clears).
2.
Press F5 (Refresh).
3.
Check the total item count in the Unread list.
4.
Result: Count is exactly 400. The content is a mix of genuinely new items and random old items needed to fill the quota up to 400.
Expected behavior: After "Mark all as read" + refresh, the Unread list should show only genuinely new items (0 if no new content arrived), not backfill from history to meet a quota.
System Information:
•
BlindRSS version: 1.65
•
OS: Windows
•
Screen Reader: NVDA.

Note:
Thank you for creating this reader. The fact that it's lightweight, not bloated with unnecessary features, simply works with screen readers, and — unlike some other projects — is still actively developed, is truly valuable.

I have observed a consistent behavior suggesting a hardcoded limit or buffer issue. After marking all as read and refreshing (F5), the application repopulates the "Unread" list to match exactly 400 items total. The Behavior (Quota filling): The application seems to prioritize filling the list to 400 items over respecting the "Read" status. • The total count is always 400. • It combines Newly arrived items and Resurrected old items. • Example: If there are 2 brand new items, the app resurrects 398 old items (dating back to e.g., Jan 22nd) to reach the count of 400. Hypothesis: This suggests a logic error where a LIMIT 400 (or buffer size) is applied before correctly filtering out the locally "Marked as read" items during the fetch/refresh process. The app effectively says: "Show me the last 400 items from the feed," ignoring that I just marked them as read locally. Steps to reproduce: 1. Menu -> File -> Mark all items as read. (List clears). 2. Press F5 (Refresh). 3. Check the total item count in the Unread list. 4. Result: Count is exactly 400. The content is a mix of genuinely new items and random old items needed to fill the quota up to 400. Expected behavior: After "Mark all as read" + refresh, the Unread list should show only genuinely new items (0 if no new content arrived), not backfill from history to meet a quota. System Information: • BlindRSS version: 1.65 • OS: Windows • Screen Reader: NVDA. Note: Thank you for creating this reader. The fact that it's lightweight, not bloated with unnecessary features, simply works with screen readers, and — unlike some other projects — is still actively developed, is truly valuable.