Formatted Messages

Ideas for ADC may be presented here for others to review and point out flaws or further improve the idea.
Forum rules
If you have an account on the wiki, remember to update the ADC Proposals page for new ideas.

http://dcbase.org/wiki/ADC_Proposals_list
adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Formatted Messages

Post by adrian_007 » 15 Jun 2008, 13:16

i've got an idea for adc extension.
FMSG stands for FormattedMSG.

idea is simple, when sending a message to chat for ex. we're adding a flag to it with parameter, like BBC or HTML and depending on it, message would be formatted on chat window.

no details atm.

what you think about it?

blastbeat
Member
Posts: 53
Joined: 10 Jan 2008, 19:56
Contact:

Re: extension idea

Post by blastbeat » 15 Jun 2008, 13:25

F stands already for feature broadcast

Pietry
Senior Member
Posts: 328
Joined: 04 Dec 2007, 07:25
Location: Bucharest
Contact:

Re: extension idea

Post by Pietry » 15 Jun 2008, 13:39

The extension needs to have a unique 4 letter code, so FMSG is ok, it has nothing to do with feature broadcast. Perhaps you think of adding a new command to the protocol ( included in the extension ) ?
Just someone

blastbeat
Member
Posts: 53
Joined: 10 Jan 2008, 19:56
Contact:

Re: extension idea

Post by blastbeat » 15 Jun 2008, 13:54

ah i see, i thought he means commands like "FMSG text..."; would be confusing

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: extension idea

Post by adrian_007 » 15 Jun 2008, 14:15

well i'm not quite sure how it could be done, but for example to normal chat message we're adding sth like

Code: Select all

FTHTML
and then message is formatted in html 'mode'

sth like pm flag if i'm right

blastbeat
Member
Posts: 53
Joined: 10 Jan 2008, 19:56
Contact:

Re: extension idea

Post by blastbeat » 15 Jun 2008, 16:05

i have some questions:

how does a client know, that another client supports formatted messages or should the client send messages anyway?
should a hub dispatch a formatted broadcast message to all even if some users in hub doesnt support it?

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: extension idea

Post by adrian_007 » 15 Jun 2008, 16:12

how does a client know, that another client supports formatted messages
client should place FMSG in supports. if feature isn't supported, hub dispatch... hmm, now what should be:
1. remove flag.
2. remove all formatting tags. [this is better]

blastbeat
Member
Posts: 53
Joined: 10 Jan 2008, 19:56
Contact:

Re: extension idea

Post by blastbeat » 15 Jun 2008, 16:19

so the client with no FMSG support gets a messages mixed up with html code etc?

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: extension idea

Post by adrian_007 » 15 Jun 2008, 16:22

now that is the question how it should be solved :)

because we don't now when we want to dispatch and when we don't want.
for example client can support only certain tags, all other should be leaved unformatted. message with FT flag should be cleaned up from this tags... but this can f*** up the message depending on content... this have to be discussed.

Pietry
Senior Member
Posts: 328
Joined: 04 Dec 2007, 07:25
Location: Bucharest
Contact:

Re: extension idea

Post by Pietry » 18 Jun 2008, 08:29

Well, in the general ADC idea, if the client receiving FT flag doesn't know it, it's just ignored. If the hub doesn't know that flag, it sends it anyway to designed clients.
To avoid sending FT flags to unsupporting clients, one can send a broadcast message by example:
FMSG +FMSG <html>This\sis\smy\shtml</html> FTHTML
using a feature broadcast message to clients supporting FMSG only.
and to the rest of the clients ( non FMSG )
FMSG -FMSG This\sis\smy\shtml
or something similar...

My suggestion is to rename FMSG to MSGF or something, to avoid confusion....

Also in the general respect between clients and hubs, the hub has no right to edit client's messages.
Just someone

Post Reply