multi user chat

[GoogleCodeExporter]

implement some kind of multi user chat

Original issue reported on code.google.com by prof7...@gmail.com on 11 Feb 2008 at 5:19

[GoogleCodeExporter]

Will one TorChat instance act as a server? Will it be able to work via the web? 
Issue
22 and issue 25 talk about managing identities, and having a web interface to
TorChat. I think if multi-user chat is implemented, I would like to invite 
others to
participate via a website.

Original comment by tahc...@gmail.com on 15 May 2008 at 6:18

[GoogleCodeExporter]

every torchat instance will also be able to act as a conference server. A web
interface is not planned at the moment, but sounds interesting. There will be a 
small
(~20 lines) command line version to run as a conference server daemon only. 
This will
also serve as an example implementation how to write own programs using the 
tc_client
module.

Original comment by prof7...@gmail.com on 15 May 2008 at 11:32

[GoogleCodeExporter]

This sounds very exciting

Original comment by tahc...@gmail.com on 15 May 2008 at 4:06

[GoogleCodeExporter]

Original comment by prof7...@gmail.com on 25 May 2008 at 7:29

• Added labels: Milestone-Release1.0

[GoogleCodeExporter]

Need a feature to can make  Puplic and Hidden Channels for Multi User Chat.

Original comment by defender...@gmail.com on 6 Jun 2008 at 5:54

[GoogleCodeExporter]

I know I'm bumping a two year thread. (Sorry) 

However looking at Comment #5, is this going to be implemented as a client 
server model. Where you could opt to run a service similar to a IRC server. The 
other option would be much like MSN and other chat providers just allowing a 
group chat where you invite members of your buddy list.

Original comment by jim.hew...@gmail.com on 11 Jan 2011 at 5:34

[GoogleCodeExporter]

Last week I created a branch to work on this feature (but did not yet start the 
work). The idea is basically the following:

* each client can act as a conference server.
* you can create rooms on your own client, rooms can be public or hidden
* rooms can be temporary or permanent (survive a restart)
* you can join existing rooms on any other clients (but not create rooms there)
* public rooms will be advertised by the buddy and listed in his profile and 
the context menu where you can join them with one moue click
* hidden rooms can only be joined when you know the exact name (the name can be 
made as cryptic as a password and effectively IS the password)
* rooms can be bookmarked, they will appear like an entry in the buddy list 
with a different icon

once the above basic functionality is implemented and working I will merge the 
muc branch back into the trunk and make a release

Later some more things can be added, like giving other users OP privileges in 
rooms that you have created, the ability to ban users (which will make it look 
like the room does not exist anymore for this user), rooms with member lists 
(they are only visible for people on a list that is maintained by the room 
owner or an OP) and all such things which will be easy to implement once I have 
the basic infrastructure working.

Original comment by prof7...@gmail.com on 11 Jan 2011 at 12:30

[GoogleCodeExporter]

Why? This is just SSL IRC through Tor. It'd be a better solution if it was done 
that way.

Original comment by georgeha...@gmail.com on 1 May 2011 at 9:53

[GoogleCodeExporter]

Using XMPP as a base and add the tor layer could be a good idea.

XMPP already handle rooms and all the chat stuff.

It's maybe more work around decentralizing the server part, than redoing chat 
part.

Some kind of local wrapper between Tor and XMPP, so any XMPP clients could 
connect to it.
The local wrapper acts like a XMPP server which speak with other wrapper 
through tor.

Original comment by microAl...@gmail.com on 12 May 2011 at 10:02

[GoogleCodeExporter]

hmmm to prevent spoofing in small rooms (under 10 members), can't we just make 
a client send out duplicate messages to all listeners? (or hashes)

The viewers can then compare the message with the designated server via hashes. 
Or totally bypass the need for servers, if its broadcast only. Broadcast only, 
means a participant can leave the channel without taking it down because theya 
are hosting it.

Original comment by akimbomi...@gmail.com on 22 Jun 2011 at 4:51

[GoogleCodeExporter]

hey guys, tabs would be great! ;)

Original comment by lukas.daniel2@googlemail.com on 25 Jul 2011 at 12:56

[GoogleCodeExporter]

I'd love to see this feature too! :)

Original comment by hostfat on 3 Jan 2012 at 6:26