Torchat - Project Hosting on Google Code
To avoid any potential confusion: This product is produced independently from the Tor® anonymity software, I am not related with or sponsored by torproject.org. TorChat is making use of the Tor® client software and the Windows version comes bundled with original Tor binaries but TorChat itself is a completely separate project developed by different people. TorChat is released as Free Software (GPL). +++ Feb-05, 2012: This project has been moved to github +++ There are new files in the download section at github: Further development of TorChat will continue at github, effective immediately. below is the old project page for historic reasons. If you like this software then maybe you want to buy me a beer. to call for the waiter. Alternatively there is also a BitCoin address: 18hmynLnHC44XiGiiPqfuTL3M4xPeJ5KqW TorChat just runs from an USB drive on any Windows PC. Tor location hidden services basically means: Linux
Relay Configuration Instructions
The Tor network relies on volunteers to donate bandwidth. The more people who run relays, the faster the Tor network will be. If you have at least 2 megabits/s for both upload and download, please help out Tor by configuring your Tor to be a relay too. You can run a Tor relay on pretty much any operating system. Tor relays work best on current distributions of Linux, FreeBSD, NetBSD, and Windows Server. The best approach for most users is to run your relay on Debian or Ubuntu using the system Tor package — the deb takes care of running Tor as a separate user, making sure it has enough file descriptors available, starting it at boot, and so on. Configure Tor by editing the torrc file Tor's configuration file is named 'torrc'. Locate the file on your system, open it with a text editor and add the following lines: ORPort 443 Exitpolicy reject *:* Nickname ididntedittheconfig ContactInfo human@... Tor will use all your bandwidth if you don't set limits for it. Make sure your relay is reachable
TorChat
TorChat is a decentralized anonymous instant messenger that uses Tor hidden services as its underlying Network. It provides cryptographically secure text messaging and file transfers for business dealings, and confidential communication between doctors and their patients.[1][2] The characteristics of Tor's hidden services take care that all traffic between the clients is encrypted and that it is extremely difficult (if not impossible) to tell who is communicating with whom and where a given client is physically located. In TorChat every user has a unique alphanumeric ID consisting of 16 characters. This ID will be randomly created by Tor when the client is started the first time, it is basically the .onion address of a hidden service. A fork was released for Mac OS X in the summer of 2010 by a French developer. See also[edit] References[edit] External links[edit] TorChat repository at GitHubTorChat for Mac OS XTorChat repository at GitHub
Web Real-Time Communications Working Group Charter
The mission of the Web Real-Time Communications Working Group, part of the Ubiquitous Web Applications Activity, is to define client-side APIs to enable Real-Time Communications in Web browsers. These APIs should enable building applications that can be run inside a browser, requiring no extra downloads or plugins, that allow communication between parties using audio, video and supplementary real-time communication, without having to use intervening servers (unless needed for firewall traversal, or for providing intermediary services). Scope Enabling real-time communications between Web browsers require the following client-side technologies to be available: Success Criteria To advance to Proposed Recommendation, each specification is expected to have two independent implementations of each feature defined in the specification. Out of Scope The definition of any new codecs for audio and video is out of scope. Deliverables Recommendation-Track Deliverables Media Stream Functions Other Deliverables
This Could be Big: Decentralized Web Standard Under Development by W3C
Imagine a web where our browsers connected directly to each other to do voice, video, media sharing and run applications, using P2P and real-time APIs, rather than going through centralized servers that controlled traffic and permissions. That’s a potent idea and if implemented properly could future-proof a part of the web from authoritarian crack-downs, disruptions by disasters and more. It could also establish a permanent lawless zone of connected devices with no central place to stop anyone from doing anything in particular. It just so happens that something like that may now be under development in the most official of venues. The World Wide Web Consortium (W3C) announced today the formation of a new Web Real-Time Communications Working Group to define client-side APIs to enable Real-Time Communications in Web browsers, without the need for server-side implementation. Below: Here’s how Opera described its Unite technology at launch two years ago.
Related:
Related: