meshbay.git/packages/meshbay-hub/src/meshbay_hub/api/invite_links.py, branch 0.16MeshBay — read-only public mirrorhttps://git.meshbay.org/meshbay.git/atom?h=0.162026-09-23T17:30:47Zfix(hub): a redeemed invitation link leaves the owner's list2026-09-23T17:30:47ZChristophe Bessoncbesson@gmail.com2026-09-23T17:30:47Zurn:sha1:95cec0e0bbc28e930f297f44bbd3dbf4d63f0bc2
The list under "Invite by link" answered every ticket the group had ever
minted, so a link that somebody had already used sat there saying "used by
<name>" for the thirty days of KEEP_REDEEMED — beside the member row it had
just produced, and above the links that still wait for somebody, which are
the only ones there is anything to do about. The node's own `member list`
had never shown them: it selects `used_at IS NULL`.
The listing now selects `redeemed_by IS NULL`, and drops the `redeemed`
status and the `redeemed_by` field with it. The row itself still lives for
KEEP_REDEEMED, which is what lets a reload or a second tab of the invitation
page be answered rather than refused; its comment says that now instead of
naming a list it is no longer in.
The SPA filters too, because the desktop client's copy of this interface can
be newer than the hub it is signed into.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
feat(hub): invitation-link tickets bound to a verified address2026-09-23T15:46:48ZChristophe Bessoncbesson@gmail.com2026-09-23T15:46:48Zurn:sha1:998f9c69308ee88fac36cfb77dfb6d07c6fa926a
group_invite_links holds sha256(ticket) and the invitee's address blind
index; redeeming grants membership to that account only. Owner-only
create/list/cancel (a node token may create, never mail), 20 outstanding
per group, optional mail written by the hub itself and capped at 10 per
sender per day (mail.invite_link_daily_cap). MESHBAY_DESIGN.md §3.4 now
carries the whole link design.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>