Onion Services terminology - second iteration

Description

The first iteration dealt with the references to Onion Services and onion sites.

Here I propose a discussion (or just ask if that's already settled) about how to refer to other Onion Services elements.

Discussion

1. How to refer to Onion Service keys? Shall we also support ".onion keys" and ".onion descriptors", to explicitly indicate that we're telling about something bound to an Onion Service address?
2. How to refer to the what some call the "clearnet", i.e, the one not accessed via Tor. Vanilla internet? Regular internet?
3. How to refer to an Onion Service that isn't accessible via the "regular internet"? "Pure-onion Service"? "Onion-only Service?"
4. Document references on the "there is not Dark Web" topic.
5. Include definition of "censorship resistance": content cannot be removed from the internet; whereas bridges offers censorship circumvention (allows users to connect to the Tor network). This need to be explained during presentations and documents. Otherwise people will confuse Onion Services with another kind of bridges.
6. How to Remove harmful terminology, such as master.

Please feel free to include more questions or to ignore this if I'm being to exaggerated in proposing this :)

Tasks

• Update the Onion Serviced Terminology page with:
  • The results of the points above.
  • Restricted Mode as the new term for Client Authorization. Moved to tpo/onion-services/onion-support#261tpo/onion-services/onion-support#261.
• Arti's onion-name might conflict with the general meaning of Onion Names. Should it be onion-address instead? Discussed initially in the 2024-12-05 Onion Services working group meeting: seemed reasonable, but need to check first if there was a reason that made "onion-name" be used in the first place.
• How to Remove harmful terminology, such as master:
  • Consider making a quick inventory of the terms we need to change.
  • Create tickets plus transition plans to avoid disruptions. Old names can be mentioned in docs, for historic purposes.
• Check other references and best practices on terminology. Examples:
  • Effective Terminology in IETF drafts
    • draft-gondwana-effective-terminology-01 - Effective Terminology in IETF drafts
  • Info | terminology@ietf.org - IETF Mailman 3 Lists