Opened 2 years ago

Closed 9 months ago

#26068 closed defect (fixed)

better describe bridges vs. relays in the glosary

Reported by: cypherpunks Owned by: metrics-team
Priority: High Milestone:
Component: Metrics/Website Version:
Severity: Normal Keywords:
Cc: metrics-team Actual Points:
Parent ID: #31281 Points:
Reviewer: Sponsor: Sponsor30-can

Description

Child Tickets

Change History (7)

comment:1 Changed 2 years ago by karsten

Cc: metrics-team added

Agreed, the definitions are slightly confusing. Here's what we have right now:

bridge: a relay whose existence is non-public and which can therefore provide access for blocked clients, often in combination with pluggable transports, which registers itself with the bridge authority.

relay: a publicly-listed node in the Tor network that forwards traffic on behalf of clients, and that registers itself with the directory authorities.

I wonder if we should say server rather than node or even relay as the broader term for a relay-or-bridge thing. After all, we also have a "Server" category on the website that includes relays and bridges.

irl, would you be able to check what the other glossaries use here? Would this change move us further into their direction or in an opposite direction?

comment:2 Changed 9 months ago by karsten

Priority: MediumHigh

Changing priority of all defects in Metrics/Website to high to get these resolved soon.

comment:3 in reply to:  1 Changed 9 months ago by karsten

Status: newneeds_review

Replying to karsten:

I wonder if we should say server rather than node or even relay as the broader term for a relay-or-bridge thing. After all, we also have a "Server" category on the website that includes relays and bridges.

We're already using these terms, so let's reflect this in our glossary. We can always adapt to a single Tor-wide glossary if/when one exists.

Please review commit 145288c in my task-26068 branch.

comment:4 Changed 9 months ago by gaba

Sponsor: Sponsor30-can

comment:5 Changed 9 months ago by gaba

Parent ID: #31281

comment:6 Changed 9 months ago by irl

Status: needs_reviewmerge_ready

LGTM.

comment:7 Changed 9 months ago by karsten

Resolution: fixed
Status: merge_readyclosed

Thanks for the review! Merged and deployed. Closing.

Note: See TracTickets for help on using tickets.