Search the Community

Showing results for tags 'mail'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • BitTorrent Client
    • Common Errors and Solutions
    • Announcements
    • General Discussion
    • Troubleshooting
    • Feature Requests
    • BitTorrent Pro Support
  • BitTorrent Mobile
    • BitTorrent Android
    • BitTorrent Remote Apps
    • BitTorrent Remote Web
  • Developers
    • Announcements
    • General Discussion
  • BitTorrent Bleep
  • Project Maelstrom
    • Developer Discussion
  • BitTorrent Web
    • BitTorrent Web Client

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. I had what I think is a great idea which I tried to post in the idea bank, but something went seriously wrong. I think the idea is extremely disruptive and has huge implications for privacy, so I wanted to at least post it here in case anyone shares my enthusiasm about it. Essentially it's a BTSync-like, server-free distributed mail application/protocol based on the bittorrent protocol, using public/private keys for encryption. Here is the description in revised form that I tried to post to the idea bank. I hope it's clear. You can also read a more layman description here: Let me know what you think. -------------- A BTSync-like application/protocol using public/private keys to facilitate encrypted, text-based communication and file transfer between clients. (Mail with optional attachments) The client application will create one (or more) public/private key set(s). It will have an contact list that holds public trusted keys received from other users. These serve as email addresses when sending messages to users. (Stores public keys as unique contact identifiers [email addresses] for communication) The use of several key sets could be used for grouping contacts, or a user could potentially use a separate key set for each contact in their list. Each contact is assigned a default local key set that acts as the 'sender' of a message. (Optionally different sender keys [addresses] when communicating with different contacts) Sending a message (with or without attachment) will be encrypted to a contact's public key, and signed with the chosen local private key. Recipients' devices are found through DHT, trackers, etc. Once a connection is established, transfers of the message begins. The client could also function as pseudo real-time chat, showing online status of other clients that have authorized your public key. Only authorized keys will retain an active connection and receive updated status from other contacts. Private keys on the client can be imported to other devices that a user frequently uses, essentially allowing a user to have identical mail clients on multiple devices (home PC, phone, etc). Mail contents on each device sharing a private key would automatically be synced.