Re-ping everyone if content changes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
If a pertinent mf2 attribute (p-title, p-summary, e-content) on an entry changes, pings should be re-sent to all targets, not just the ones where URLs changed.
However this should only happen when actual entry content changes and not based purely on the overall content hash (eg nav links, “15 minutes ago” publish times, etc)
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
Start by tracing how Pushl extracts p-title, p-summary, and e-content and how it computes entry and overall content changes before sending pings. Check existing tests around URL changes and content hashes, then define completion as re-pinging all targets only for pertinent entry-content changes while ignoring unrelated hash changes such as navigation links or relative publish times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100