Search the Community
Showing results for tags 'chat'.
Found 2 results
A really bad demonstration of P2P messaging is Skype. Here are a few reasons it is a bad demonstration: If you send a user a message and then go offline, and they come online, they will not receive your message until you are online again.If you send a user a message who is appearing offline, you can tell that they are appearing offline because the spinning message icon turns to a sent checkmark which defeats the purpose of appearing offline if you are avoiding someone.Video calls constantly drop out.Skype's P2P is centralized in a sense which is completely pointless since they allow the government to snoop through everything.It takes a lot of battery on mobile phones.It still requires a data plan or internet plan / connection which in Canada is extremely controlled and abused. We pay roughly 70-80 dollars a month for 4GB of data and unlimited text messaging and limited calling.To make BitTorrent chat to be really useful, we need to start developing phones with multiple wireless network adapters in them that connect to each other and create a peer to peer chained network that turns into a p2p internet connection that requires no centralized connection point or server. Basically what tor is except every phone is a web server that connects to other web servers and hosts and shares encrypted pieces of information. Once we can eliminate ISP's the people will be in control of prices, and the people will not pay for these ridiculous services. If every person who had a wireless router could chain their routers together they could span the entire city and communicate citywide without any ISP or radio tower. Yes it would be slow at first, but slow is better than censorship. I am interested to hear all your thoughts. I have been thinking about this for a long time, but I am not an electronic engineer I am just a PHP programmer.
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.