Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #6600

Closed
Open
Created Aug 13, 2012 by Mike Perry@mikeperry

Write proof-of-concept hidden service chat, email, etc applications

Hidden services don't have to be just for publishing. They are arbitrary communication endpoints.

We could prototype hidden service-based chat and email by bundling local XMPP and SMTP servers for use with Tails.

Client software developed for #6583 (moved) could then be used almost as-is to communicate with other hidden service endpoints.

The benefits of hidden service communications are that you do not reveal your social graph to the network or even to any centralized chat or email infrastructure, and you get end-to-end encryption and authentication for free.

The key things that makes this a large project are that we need solid integration with client software, and the XMPP and SMTP servers have to "just work" right out of the box. If this integration and deployment is not seamless, almost no one will use hidden services this way, and the few who manage to do so will not have anyone to communicate with.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking