Limited Feed Snapshot

Open
#1,158 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, java
Domain
mobile

Research direction

No files or tests are named. Start by locating the Android app's feed-loading and refresh entry points, then determine how a fixed snapshot, refresh timing, and the non-reversible setting could be represented. Done would require agreed product behavior, implementation, and tests for loading, persistence, refresh timing, and disabled refresh controls.

Written by the indexing model from the issue text.

Description

I don't know if this is in any way within the intended scope of the project, but I'll just ask:

Would you consider a sort of Anti-addiction setting? It could for example work like this:

  • A set number of posts, say 100, is loaded from all subscribed subreddits in the order it would have normally been loaded. There is no 'Load more posts'.
  • This data is kept and not refreshed - the feed stays exactly the same. Even the UI interaction of refreshing isn't available.
  • Only every 24 hours - or whenever RedReader hasn't been opened for 10 hours - the content is refreshed and a new feed is generated
  • This setting cannot be turned off from within the app once activated - one would have to reinstall / clear user data

This would still allow the user to visit specific subs, go on deep dives etc., but the psychological effect of knowing there will be no new posts in your feed until tomorrow, no matter how much you refresh and scroll, might be quite significant.

Thank you for considering!

Dominant language
Java
Stars
2.7k
Forks
527
Avg merge
20d 10h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QuantumBadger/RedReader

All issues in QuantumBadger/RedReader

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.