|
|
# [The Onion Plan](202209MeetingOnionPlan) - Tor Dev Meeting 2022
|
|
|
|
|
|
## About
|
|
|
|
|
|
* Facilitator: @rhatto and @raya
|
|
|
* Who: all interested.
|
|
|
* Duration: 1 hour.
|
|
|
* Description: the usability improvements of Onion Services are an outstanding
|
|
|
challenge being discussed for years. Now that the protocol v3 is successfully
|
|
|
deployed, it may be the time to think about the roadmap for the next steps,
|
|
|
including Onion Names, fundraising and a future Onion Service adoption
|
|
|
campaign.
|
|
|
|
|
|
## Presentation
|
|
|
|
|
|
* [Slides in PDF](202209MeetingOnionPlan/intro.pdf)
|
|
|
* [Slides in Markdown](202209MeetingOnionPlan/intro)
|
|
|
|
|
|
## Notes
|
|
|
|
|
|
### Priorities
|
|
|
|
|
|
* We need to have a strong and healthy network in order to have onion services.
|
|
|
|
|
|
### The four tracks
|
|
|
|
|
|
Four main things to talk about:
|
|
|
|
|
|
* 1. Onion Services Health.
|
|
|
* 2. Usability of Onion Services:
|
|
|
* Reachability, will Lets Encrypt support onion addresses?
|
|
|
* Suggestion to implement something like BridgeMoji for Onion Addresses to
|
|
|
improve memorability and famliarity of addresses:
|
|
|
* Some people does not find it very useful for bridges neither.
|
|
|
* This problem is very important for attendants and we got derailed a
|
|
|
little bit with proposals to solve it.
|
|
|
* [Proposal 279][] was written aiming for a naming system API.
|
|
|
* With Sauteed onions we can implement something, but we need Tor Browser to query an API.
|
|
|
* Crazy proposal REDACTED REDACTED REDACTED.
|
|
|
* If Onion Location is set to a v2 address and you have selected use onion
|
|
|
address, Tor Browser breaks. Outstanding issue and low hanging fruit to target.
|
|
|
3. Tooling:
|
|
|
* It is difficult to plan integration with DevOps because the landscape
|
|
|
changes and and there are many ways to do.
|
|
|
* Maybe we should add different modules for ansible or qubernets, etc.
|
|
|
4. Outreach:
|
|
|
* Gather a list of organizations that need onion services and onion location.
|
|
|
|
|
|
## Next steps
|
|
|
|
|
|
[Proposal 279]: https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/proposals/279-naming-layer-api.txt |