joebush

Members
  • Content Count

    85
  • Joined

  • Last visited

  • Days Won

    3

joebush last won the day on August 23 2014

joebush had the most liked content!

Community Reputation

12 Good

About joebush

  • Rank
    Advanced Member
  1. Since the original purpose of this thread was to spur the interest and development of BT Chat, the thread is now closed. Any further discussions about features, progress, etc. for BT Chat should be taken to appropriate threads. (I apparently can't close the thread, but we can pretend I did. Maybe a mod can help me out.)
  2. About 6 months ago I posted here with the idea of a decentralized, secure mail/chat client. (http://forum.bittorrent.com/topic/22678-bittorrent-mail-secure-distributed-mailmessaging/) Since then, Bittorrent has made a statement about Bittorrent Chat (Bleep), which I'm sure has excited a lot of people that are concerned with the state of privacy in today's digital world. I've been thinking about an expansion to Bleep which I feel is a natural next step, and definitely important for the same reason that many feel that chat and mail should be decentralized. You can read my post about it here for a layman's argument and description: http://techrace.wordpress.com/2014/02/22/decentralizing-social-media/ Bittorrent Chat for Social Networking Starting with the assumption that social networking is merely an expansion of a multi-user chat system, and based on the information that has been provided by Bittorrent about the Bleep client they are working on, I suggest the following. Each chat session has a unique identifier. (stated by Bittorrent) Allow for multi-user chat, with each user being identified by their public key, and each participant adding messages using the chat identifier and their private key. Expand each chat session in such a way that it requires a header text, with optional media attachments. This header will be the original post which is 'owned' by the creator, and further replies from recipients are added as comments. When starting a chat (referred to as post after this), recipients are chosen from the creators contact list. The post will be sent to the recipients based on their public keys using the underlying chat communication protocol. Recipients' clients will receive the post from the original sender, or any other recipients that have already received the post. Recipients of the post will share any comments with other recipients with access to the post based on the public keys in the recipient list. When a user opens a contact from their contact list, a page is opened with a consolidated list of the posts the contact has created and shared with the user.There are many aspects of a final solution that I've ignored, since the idea here is to try to define the basic functionality for social networking to be implemented using Bleep. I hope the Bleep team sees this post and thinks it's a useful, natural extension to what they're already working on.
  3. I still argue a user can't have a guarantee of control. A client can always be created that won't delete messages. Thanks for the link. That's interesting. Haven't seen that one before. I guess we'll have to see what happens, but I think there needs to be a completely open de facto standard (and hopefully official, eventually) before this can take off. Once that's in place, anyone can make a client, and this can then be used by the masses for any correspondence purposes that they use email and chat for today.
  4. Any system that will allow true distributed messaging will not allow the user to retain control. As long as there is anonymity and good encryption, this isn't a real problem in my opinion.
  5. Yes! They just started development of a BitTorrent secure chat client!
  6. Btw, if a dev here can get this posted in the idea bank for me, that would be great. It kept telling me I'm not authorized and logging me out.
  7. 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: wp.me/poSvv-n 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.