Protocols/MSNP/MSNC/Custom Emoticons: Difference between revisions

From NINA Wiki
Jump to navigation Jump to search
m (added navigation)
 
m (1 revision imported)
(No difference)

Revision as of 00:23, 29 May 2020

| style="font-size: 95%; text-align:center; color:#000000; background-color:#499feb" | MSNC |- | OverviewMSNObject |- | Client Capabilities |- | style="font-size: 95%; color:#000000; background-color:#499feb; text-align:center;"|P2P protocol |- | TransportsMSNSLP |- | style="font-size: 95%; color:#000000; background-color:#499feb; text-align:center;"|Headers |- | P2Pv1 Binary headers |- | P2Pv2 Binary headers |- | style="font-size: 95%; color:#000000; background-color:#499feb; text-align:center;"|Transfers |- | Display Pictures |- | Custom Emoticons |- | File Transfer |-

| style="font-size: 120%; color:#000000; margin-top: 0.5em; background-color:#499feb; text-align:center;"|Overview |-

Custom emoticons

Custom created emoticons are being requested on the same way as Display pictures are. Only the client received the MSNObject for a custom emoticon on a different way. Immediately before someone sends you a message containing custom emoticons, you will receive a message of the type text/x-mms-emoticon, containing information about all custom emoticons used in that message:

MSG 1 N 232
MIME-Version: 1.0
Content-Type: text/x-mms-emoticon
alias1 TAB MSNObject1 TAB alias2 TAB MSNObject2 TAB

The alias is the text you should replace with the custom emoticon in messages. It should not be replaced when inside a URL. Where the MSNObject points to a emoticon file, some fields have different values. The Type field for example has now the value 2.

Example content from a text/x-mms-emoticon with the two icons "(tux)" and "(baaha)":

(tux) <msnobj Creator="alice@example.com" Size="978" Type="2" Location="TFRC5.dat" Friendly="AAA=" SHA1D="Uz3MQadmIWHed3saSdwcTo/Tc7U=" SHA1C="e7vZQCbXV30xf3gngY3P3slZhts="/> (baaha) <msnobj Creator="alice@example.com" Size="691" Type="2" Location="TFR3FA.dat" Friendly="AAA=" SHA1D="as1WxRoW0FXQFVrERtCC1Hec8i8=" SHA1C="AeZUBbzp5rI7tlZJ++ikrO4SeUk="/>

The SHA1C hashes do not match, but maybe I'll fix that later or someone else will.