Opened 5 years ago

Last modified 2 years ago

#15060 new enhancement

Decide the fate of MyFamily

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: needs-proposal, needs-design myfamily tor-relay
Cc: nusenu@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

See discussion on #5565 and #6676. It may be that the family declaration is making guard selection worse, and if so, maybe we should not do guard selection in the same way. Having some paths with all three nodes in the same family scares me, though.

We could do better than the current family system using certs as described in prop220. First we should decide whether we want to keep families at all, though.

Child Tickets

TicketTypeStatusOwnerSummary
#4998defectclosedJigsaw52MyFamily as a list
#5565enhancementreopenedMyFamily should provide an alternate non-idhex subscription mechanism
#6676taskclosedNuke ‘MyFamily’
#12574defectclosedInclude unnamed family members in family

Change History (15)

comment:1 Changed 5 years ago by nickm

Status: newassigned

comment:2 Changed 5 years ago by tyseom

Cc: nusenu@… added

comment:3 Changed 5 years ago by nickm

Keywords: 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:5 Changed 4 years ago by nickm

Keywords: SponsorU removed
Sponsor: SponsorU

Bulk-replace SponsorU keyword with SponsorU field.

comment:6 Changed 4 years ago by isabela

Sponsor: SponsorUSponsorU-can

comment:7 Changed 3 years ago by nickm

Keywords: SponsorU-deferred added
Sponsor: SponsorU-can

Remove the SponsorU status from these items, which we already decided to defer from 0.2.9. add the SponsorU-deferred tag instead in case we ever want to remember which ones these were.

comment:8 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:9 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:10 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:11 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:12 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:13 Changed 2 years ago by nickm

Keywords: 027-triaged-1-out removed

comment:14 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:15 Changed 2 years ago by nickm

Keywords: needs-design myfamily tor-relay added; SponsorU-deferred removed
Severity: Normal
Note: See TracTickets for help on using tickets.