Following / follower system
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
* Think about follow / following system and aggregating streams
* Right now for maximum versatility maybe have a "EventAggregator" model that has a m2m with GenericForeignKey
* Event Aggregator should also have a GFK "owner" with the user (or whatever)
* Automatically de-dupes
* Need to think if there are any performance hacks for this
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
Start by reviewing the existing activity-stream models and entry points, then assess how a following system would interact with them. Define the EventAggregator relationships, ownership, stream aggregation, automatic de-duplication, and performance expectations before implementation; done means these design decisions are settled and the resulting behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100