randomize Unfollow and follow activity further
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 692
- Forks
- 103
- Avg merge
- 3m
- Merged PRs (30d)
- 4
Description
I think it is very suspicious and will lead to detection that the follow/unfollow activity never mixes.
Meaning: it always starts with ONLY unfollowing and then ONLY follows.
It would be much less suspicious if it would spread the unfollows out randomly across the active time.
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
The issue does not name any files or tests. Start by locating the follow/unfollow activity scheduling entry point and review how the active period is ordered. Done means unfollow actions are distributed among follow actions rather than occurring in one uninterrupted phase; add or run the relevant scheduling tests if the project provides them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100