Let testers hide ignored organizers from ordinary discovery #21

Open
opened 2026-11-01 20:11:39 +00:00 by viacheslavshuka · 0 comments

Outcome

Testers need control over whose sessions they discover. Add a website ignore list and a matching policy for discovery consumers.

Acceptance criteria

  • Users can add and remove organizers from their own ignore list through website forms. Provide a browser route that bot navigation can open.
  • A session matches the ignore filter if any accepted organizer appears on the tester's list, including an accepted co-organizer.
  • The matching policy excludes matching sessions from ordinary discovery. A Show all input includes them without changing the saved ignore list.
  • The recommendation policy rejects ignored organizers regardless of the Show all input. Browsing overrides do not change notification eligibility.
  • The policy exempts existing commitments and their important updates. Saving ignores changes no registration, approval, or capacity record.
  • The policy does not deny direct access to published details. It grants no permission to read drafts or protected links.
  • Only testers have ignore lists. No organizer-side ignore or ignore-based registration prohibition is introduced.
  • Another user cannot modify this list. The policy returns matching decisions without exposing the tester's ignore list to organizers.

Validation design

Use independent policy inputs for an ignored owner, accepted co-organizer, pending invitation, and removed organizer. Check ordinary, Show all, recommendation, and existing-commitment results.

Verify the saved list through the website and PostgreSQL. Cross-account writes must leave both lists unchanged. Saving a list must not change seeded participation records.

Dependencies

## Outcome Testers need control over whose sessions they discover. Add a website ignore list and a matching policy for discovery consumers. ## Acceptance criteria - Users can add and remove organizers from their own ignore list through website forms. Provide a browser route that bot navigation can open. - A session matches the ignore filter if any accepted organizer appears on the tester's list, including an accepted co-organizer. - The matching policy excludes matching sessions from ordinary discovery. A Show all input includes them without changing the saved ignore list. - The recommendation policy rejects ignored organizers regardless of the Show all input. Browsing overrides do not change notification eligibility. - The policy exempts existing commitments and their important updates. Saving ignores changes no registration, approval, or capacity record. - The policy does not deny direct access to published details. It grants no permission to read drafts or protected links. - Only testers have ignore lists. No organizer-side ignore or ignore-based registration prohibition is introduced. - Another user cannot modify this list. The policy returns matching decisions without exposing the tester's ignore list to organizers. ## Validation design Use independent policy inputs for an ignored owner, accepted co-organizer, pending invitation, and removed organizer. Check ordinary, Show all, recommendation, and existing-commitment results. Verify the saved list through the website and PostgreSQL. Cross-account writes must leave both lists unchanged. Saving a list must not change seeded participation records. ## Dependencies - [#14: Authenticate Telegram users through protected Quorum sessions](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/14). Supplies account-scoped authorization and persistence. ## Related work - [#47: Manage test co-organizers through accepted invitations](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/47) - [#54: Open Quorum on a filtered list of upcoming tests](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/54) - [#55: Announce matching tests once and combine deferred discoveries into digests](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/55)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
viacheslavshuka/quorum#21
No description provided.