Re: EB-lite feature requests

Sometime Today, Meredydd Luff assembled some asciibets to say:

> Right. This is a design flaw in the whole rich-object buddy system EB keeps. 
> Each account has a complex structure associated with it, which on the plus 
> side allows complicated protocol-supplied data and contact bindings, but on 
> the other hand requires it to be a member of a contact and therefore on the 
> contact list.
> 
> Do you have any suggestions for avoiding this? Because I'm kinda stumped...

Have a dummy buddy group that isn't listed in the group/contact list.  
Dummy contacts are added to this group, and accounts added to it.  

This group does not correspond to anything on the server.  Ayttm uses 
something like __Dummy__%random%__%pid%__

%random% is decided at the start of the program.  This string is also 
not to be translated ;)

Any accounts added to this group do not get added on the server, simply 
because the core refrains from telling the service module about it.

The core really doesn't have to tell anyone about the existence of this
group or the contacts contained in it.  Consequently, the gui should
trust that the core will send it messages from people that the gui
doesn't necessarily know about.  The core can provide an
add_dummy_account or start_unknown_conversation service to the gui so
that one can start a new conversation with someone not in his buddy
list.

Thoughts?

Philip

Note: ayttm only implements it for incoming messages.