Relay member capacity limit defined in plans but never enforced #33

Closed
opened 2026-04-20 12:01:16 +00:00 by userAdityaa · 1 comment
Contributor

Description

The three pricing plans define member limits (free = 10, basic = 100, growth = unlimited) in Query::list_plans(), and the UI displays these limits in RelayDetailCard. However, neither the API nor any backend handler validates member count against these limits. A user on a free plan can admit an unlimited number of members to their relay.

### Description The three pricing plans define member limits (free = 10, basic = 100, growth = unlimited) in Query::list_plans(), and the UI displays these limits in `RelayDetailCard`. However, neither the API nor any backend handler validates member count against these limits. A user on a free plan can admit an unlimited number of members to their relay.
Owner

Yes, I'm not quite sure how to approach this. Probably add an API endpoint to zooid which allows callers to query the member list. We display the member list on the frontend too, which could be fetched via nip 86 or directly from the relay, but it would probably be best to re-use the same mechanism there by adding a /relay/:id/members endpoint to the api.

Yes, I'm not quite sure how to approach this. Probably add an API endpoint to zooid which allows callers to query the member list. We display the member list on the frontend too, which could be fetched via nip 86 or directly from the relay, but it would probably be best to re-use the same mechanism there by adding a /relay/:id/members endpoint to the api.
Sign in to join this conversation.
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/caravel#33