Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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.

  • Legacy
  • TracTrac
  • Issues
  • #11501

Closed (moved)
Open
Opened Apr 13, 2014 by George Kadianakis@asn

Improve visual identity of Tor's PTs

We've been failing with naming Tor's censorship circumvention tech for a while ('Pluggable Transports', 'obfsproxy', 'obfs3', 'obfs2', 'flashproxy'...).

We know that our users are getting better at learning these terms, but we should try to help them. I think establishing a visual identity for PTs through a logo, might help.

This way, we can put the same logo in the PT/obfsproxy homepage, and in BridgeDB, and in TBB (in the step of the wizard where you have to add your bridges), and people will learn that when they see that logo it's PT-related.

I'd currently use the obfsproxy logo: https://trac.torproject.org/projects/tor/attachment/ticket/5111/logo%20shaded.svg except if someone tells me it's a terrible idea (I admit it's more silly than confidence inspiring, but I think it gets the point across). Any other suggestions are welcome.

If people think that this is a reasonable idea, I will create tickets for the BridgeDB and TBB mods.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#11501