Protocols/MSNP/MSNC/Custom Emoticons

From NINA Wiki
Revision as of 19:13, 11 May 2022 by Animadoria (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
MSNP Protocol
MSNC
OverviewMSNObject
Client Capabilities
P2P protocol
TransportsMSNSLP
Headers
P2Pv1 Binary headers
P2Pv2 Binary headers
Transfers
Display Pictures
Custom Emoticons
File Transfer
Overview
IntroductionTermsClients
Reference
Error ListCommandsRelying Party SuiteSpotlife
Services
XMPPHTTP GatewayTabsActivities
Documentation
Development ToolsMSNP Grid
PolygamyURLs used by MSN
Documents
Protocol Versions
Version 21
Version 18
Version 16
Version 15
Version 14
Version 13
Version 12
Version 11
Version 9
Version 8
Version 2
MSNC
IntroductionP2PObject DescriptorDisplay PicturesFile Transfer
Scenarios
Microsoft Messenger for Mac
MSNP on WebTV (MSNTV)

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.