coracle/flotilla
1
6
Fork 24
Code Issues 43 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Keep track of email->signer mappings for pomade recovery #33

New Issue
Open
opened 2026-02-17 18:05:33 +00:00 by hodlbod · 2 comments
hodlbod commented 2026-02-17 18:05:33 +00:00
Owner
Copy Link
Copy Source

Imported from https://github.com/andotherstuff/universes/issues/36 by @staab on 2026-01-12T21:38:37Z

From the pomade protocol doc:

If this is used for recovery from an active session, the client should only send this request to the selected signers. If used for logging in after a password has been forgotten, it won't be known which signers hold the user's key shares, so clients will have to send this request to all known signers. As a result, if a user has multiple active sessions they may receive more than total challenges. Clients should handle this by allowing the user to paste any number of challenges, or by keeping track out of band which signers were used for a given email address.

_Imported from https://github.com/andotherstuff/universes/issues/36 by @staab on 2026-01-12T21:38:37Z_ --- From the pomade protocol doc: > If this is used for recovery from an active session, the client should only send this request to the selected signers. If used for logging in after a password has been forgotten, it won't be known which signers hold the user's key shares, so clients will have to send this request to all known signers. As a result, if a user has multiple active sessions they may receive more than `total` challenges. Clients should handle this by allowing the user to paste any number of challenges, or by keeping track out of band which signers were used for a given email address.
hodlbod added this to the Future milestone 2026-02-17 18:05:33 +00:00
hodlbod removed this from the Future milestone 2026-04-02 18:57:16 +00:00
hodlbod added the idea label 2026-04-02 19:36:33 +00:00
hodlbod added this to the Current milestone 2026-04-02 19:36:36 +00:00
hodlbod modified the milestone from Current to Future 2026-04-02 19:36:38 +00:00
bhavishy2801 commented 2026-04-06 05:19:58 +00:00
Contributor
Copy Link
Copy Source

Hi @hodlbod. Can I work on this issue?

Hi @hodlbod. Can I work on this issue?
hodlbod commented 2026-04-06 17:19:52 +00:00
Author
Owner
Copy Link
Copy Source

This one is marked "future", I'm not sure I want to add this level of complexity right now.

This one is marked "future", I'm not sure I want to add this level of complexity right now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label idea
Milestone
No items
No Milestone Future
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#33
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?