I know that it's not a perfect solution. I think I'm not skilled enough
to write a plugin for Kopete. Can't you like virtually open some Windows
in the background ? It's like having a keyboard input.
I think this is okay:
"
Bille says:
Arthur says:
Wow this sure is hard to figure out who is talking!
"
Relpace it by:
"
Bille says:\n#
--------------------------------------------
Arthur says: bla bla bla
"
...
Give the function a name, that sounds good, for instance "James the
postman", "Crossposter", "Crossconference", "imperfect conference" or so...
Ok. Just an idea. Maybe we should make all ICQ users switch to Jabber :D
Sven
Will Stephenson schrieb:
> On Sunday 28 January 2007 13:59, Sven Scheres wrote:
>
>> I do really like Kopete, but there's one thing, that would be great to
>> have:
>>
>> A kind of bridging function to do conferences. Kopete gets messages from
>> different people and automatically redirects them to those people you
>> have chosen to be in your conference. This would give you the chance to
>> do multi-protocol conferences. And I think it's not that complicated to
>> build that function into Kopete.
>>
>
> It's perfectly doable, but not very practical, one of those problems that
> distributed systems people love to play with, and we've casually discussed
> such a thing several times in the last few years. Doing this is running an
> overlay protocol over several IM systems. To make it work you need to tell
> each contact who actually wrote a message
> eg if Arthur, Bille and Charlie are conferencing and Bille is the relay:
>
> Bille relays a message by Arthur, Charlie sees:
> Bille says:
> Arthur says:
> Wow this sure is hard to figure out who is talking!
>
> To get round this, each user could run a client which strips the control
> information out of the relayed messages and presents it as a normal message.
> But when you do that you might as well get each user to run a clients which
> speak the same protocol.
>
> Another complication is, you need to detect if >1 client in the chat is
> running the relay protocol and drop already relayed messages, or you end up
> infinitely flooding the 'channel'. In a decentralised setup, each relay
> needs to label each message it forwards with a unique ID and then drop them
> if it sees them again.
>
> Feel free to code it, but there are plenty of other things that could improve
> Kopete that have a higher priority for me :). If you want real CS credit,
> write a plugin that solves the Byzantine Generals problem of shared
> information over separate channels, where some number of the nodes may tell
> lies.
>
> Will
>
>
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
