Page MenuHomecode.freespoken.nz

Separate identity and location objects
Open, To DoPublic

Description

It would be helpful to put the cryptographic identity (e.g., TLS-certified identity) of an instance into a separate object from the possibly volatile location identity of the instance — currently they're mushed together in connection details objects. That way, to solve T44, when an instance doesn't know where one of its peers is, it can identify the lost peer by its cryptographic identity when asking a mutual peer to tell the lost peer where the requester is.

The cryptographic identity of an instance could then easily be combined with a username to identify a member of an instance with a volatile location.

Event Timeline

tim created this task.Fri, Sep 7, 5:49 PM
tim triaged this task as To Do priority.