Support blocklisting of webhook servers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 82
- Avg merge
- 18h 22m
- Merged PRs (30d)
- 51
Description
While it's the subscription server exposes an endpoint to unsubscribe from the webhook notifications, it relies on the receiver to make a request. It can happen that subscribed servers are in a bad state (always returning error status), or down altogether. Currently all the subscriptions are kept regardless, which could be exploited.
One solution could be to force the subscriber to re-subscribe after a set time period, but this can be annoying, since we force the receiver to constantly re-subscribe, leading to missing notifications. Another solution could be to blacklist servers that are not healthy, keeping them for a period of time before deleting them altogether.
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 tracing how webhook subscriptions are stored and how delivery errors are handled. Define the health criteria, temporary blocklist period, and eventual deletion behavior before implementing the feature; done means unhealthy subscriber servers are blocked without requiring constant re-subscription.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100