Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
rdsys
rdsys
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #7

Closed
Open
Created Sep 17, 2020 by Philipp Winter@phwMaintainer

Design a user interface for Salmon

We need to start thinking about Salmon's user interface. In an ideal world, we would build it into Tor Browser and make it so that users will never be exposed to bridge lines at all.

For now, Salmon supports the following user-facing actions:

  1. Sign up by being invited by somebody else.
  2. Sign up by registering (we don't have a good plan for that yet).
  3. Receive a bridge.
  4. Invite somebody else to Salmon.
  5. (Optional) Take a look at your reputation and invite graph.

Tor Browser could talk to our Salmon backend (which will be part of rdsys) using a domain-fronted API, similar to how moat works.

Copying @cohosh, @antonela, @gaba, @arma, and @sysrqb.

Assignee
Assign to
Sponsor 30 - Objective 2.3
Milestone
Sponsor 30 - Objective 2.3
Assign milestone
Time tracking
None
Due date
None