Opened 3 years ago

Last modified 2 years ago

#25918 new defect

Standardize the 'onion service' name

Reported by: atagar Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Major Keywords: tor-hs
Cc: dmr Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


A recent post on tor-dev@ just got me thinking about the roadblocks we have for v2 deprecation. There's a couple I don't believe we're following in trac so lets fix that.

For me the biggest is its name. Renaming takes work, and we attempted to rename hidden services in v3 without investing the time to make it happen. We should either fix that or revert to to the old name. To move forward we need to...

  1. Have OnionService aliases for controller commands, events, descriptor fields, and anything else referencing 'HS' or 'HiddenService'.

Speaking of which, how do we plan to replace abbreviations? Having an 'OSFETCH' or 'OS_CREATED' event doesn't exactly have the same ring as their HS counterparts. ;P

  1. Adjust all our docs to be consistent about the name.

Renaming takes work. Lesson I learned from Nyx is that it works best if you draw a line in the sand and stand by it. With Nyx, version 2.0 is called Nyx (you won't find any docs saying otherwise) and version 1.x is the legacy 'arm' project.

If I was in your shoes I'd opt for the same. Either prioritize the aliases and be firm that v3 are 'Onion Services' or abort the rename. Otherwise this will live in a confusing dual-named limbo land indefinitely. ;P

Cheers! -Damian

PS. Stem and Nyx have stuck with the old name ("hidden services") and will continue to do so until tor's standardized this.

Child Tickets

#17343newAdd torrc option OnionService* alias for HiddenService*Core Tor/Tor
#25922newAdd an alias mechanism for controller commands and events, and use it for Onion ServicesCore Tor/Tor

Change History (11)

comment:1 Changed 3 years ago by teor

Please see #17343, which is about providing torrc option aliases.

Would you like to send the content of this ticket in an email to tor-dev?
Tickets aren't great places to dicsuss strategy and scheduling.

comment:2 Changed 3 years ago by atagar

Hi teor, thanks for the link! I pointed folks toward this ticket in my reply on tor-dev@.

comment:3 Changed 3 years ago by teor

I think the content of this ticket would be a great starter email for a thread on tor-dev.

comment:4 Changed 3 years ago by dmr

Cc: dmr added
Keywords: tor-hs added

Perhaps ironically adding the tor-hs keyword. (I agree that renaming things is hard.)

Last edited 3 years ago by dmr (previous) (diff)

comment:5 Changed 3 years ago by cypherpunks

Parent ID: #25955

comment:6 in reply to:  5 Changed 3 years ago by teor

Replying to cypherpunks:

Parent ID: → #25955

I think we can deprecate v2 onion services separately from the renaming process.
The people working on the tasks will make a decision when the rest of the deprecation tickets are done.

comment:8 Changed 3 years ago by teor

Parent ID: #25955

comment:9 Changed 2 years ago by traumschule

Parent ID: #25955

Sorry, i did not see, that teor removed the parent before, removing it.

Last edited 2 years ago by traumschule (previous) (diff)

comment:10 Changed 2 years ago by traumschule

Parent ID: #25955

comment:11 Changed 2 years ago by nickm

Milestone: Tor: unspecified
Note: See TracTickets for help on using tickets.