MoeraOrg / MoeraOrg/moera-issues
Story about an updated profile
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Optionally, a node may create a story in its Timeline every time something is changed in its profile. If there were several changes in a row, they should be grouped and only one story should be created. These stories are ignored by subscribers, but displayed in Web UI.
Optionally, a node may create a story in its Newsfeed (or even instants) every time something is changed in a profile of one of its subscriptions. If there were several changes in a row, they should be grouped and only one story per subscription should be created. Since the node should be subscribed to profiles of all of its subscriptions, it receives notifications about all changes in their profiles.
Contributor guide
No contributing guide indexed for this repository
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 profile-change, Timeline, Newsfeed, subscription, and Web UI implementations, then trace how profile updates are delivered. Done means grouped stories appear in the stated destinations, are ignored by subscribers where specified, and remain visible in the Web UI.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100