QuantumBadger / QuantumBadger/RedReader
Handle network losses better while browsing a thread
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
I'm using Reddit frequently while on a train. Sadly, my internet connection there is not the way I want it to be. Sometimes it's really fast, sometimes it's really slow and sometimes there's nothing.
So when I'm reading a thread I'm reacting to several comments by upvoting or downvoting. I don't test my connection before this.
And frequently I get the message that my connection dropped - but this only happenes a while after I upvoted a comment. I don't know which comment it was by then.
It would be nice if RedReader could cache my actions and try to do them again if they fail because of a network dropout.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the thread comment voting flow and its network-failure handling; done means failed upvotes and downvotes are retained and retried after a network dropout without losing track of the affected comment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100