Home › Forums › Archives › Site News & Announcements › Instant Messaging News › Windows Live Messenger News › MSN Messengers Server Protocol Updated
- This topic has 0 replies, 1 voice, and was last updated 20 years, 6 months ago by BigBlueBall News.
-
AuthorPosts
-
November 14, 2003 at 6:00 am #16269BigBlueBall NewsMember
EvilSeph for Plus!Lite
November 14, 2003
Yesterday (November 13th 2003), MSN Messenger servers were supposedly having “problems”. These problems werent reported by the MSN Messengers services status page. Given that MSN Messenger servers usually go through routine downtimes where maintenance is performed, these problems went unquestioned by the MSN Messenger “experts” at Mess.be, Messenger Plus!s forums, MSNFanatic and their forums. However, it has recently been discovered that the MSN Messenger Server Protocol has been silently modified/updated to prevent Messenger Plus! control codes from working, not to mention several other characters that are used in MSN Messenger nicknames known as “nickname tricks”. Although, despite what other sites are reporting, multi-line nicknames do work — several people have tested this theory and it has proved false, the recent protocol update does NOT prevent users from having multi-line nicknames. It does however prevent users from using Messenger Plus! colour codes, bold codes, underline codes, strikeout codes (formatting tags/codes) in their nicknames (which Patchou has already stated that hell find a way to work around it). As this is a server-side issue all you can do is wait for Patchou to discover an ample work-around for this problem. Moreover, the formatting tags and whatnot will still work in your nickname until you try and change it.
The lingering question is now: What is Microsoft up to? First they block certain words from being in your nickname, then they remove it. Next they remove the block on those certain words and now add a block for certain characters, notably Messenger Plus! formatting code characters.
What is Microsoft up to?
-
AuthorPosts
- You must be logged in to reply to this topic.