Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • rdsys rdsys
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #7
Closed
Open
Created Sep 17, 2020 by Philipp Winter@phwReporter

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
Time tracking