comparison libpurple/protocols/myspace/myspace.h @ 19247:44b9e41bde2a

No longer check the length of passwords - instead, pass the password to the servers, which will give a login failed message anyway. This avoids having a new popup just for over-long passwords, until libpurple supports per-protocol password length limits.
author Jeffrey Connelly <jaconnel@calpoly.edu>
date Wed, 15 Aug 2007 15:41:33 +0000
parents 335ebd202a7d
children 78558930d9f3
comparison
equal deleted inserted replaced
19246:335ebd202a7d 19247:44b9e41bde2a
75 75
76 /* Maximum length of a password that is acceptable. This is the limit 76 /* Maximum length of a password that is acceptable. This is the limit
77 * on the official client (build 679) and on the 'new password' field at 77 * on the official client (build 679) and on the 'new password' field at
78 * http://settings.myspace.com/index.cfm?fuseaction=user.changepassword 78 * http://settings.myspace.com/index.cfm?fuseaction=user.changepassword
79 * (though curiously, not on the 'current password' field). */ 79 * (though curiously, not on the 'current password' field). */
80 #define MSIM_MAX_PASSWORD_LENGTH 10 80
81 /* Not defined; instead have the client reject the password, until libpurple
82 * supports specifying a length limit on the protocol's password. */
83 /* #define MSIM_MAX_PASSWORD_LENGTH 10 */
81 84
82 /* Build version of MySpaceIM to report to servers (1.0.xxx.0) */ 85 /* Build version of MySpaceIM to report to servers (1.0.xxx.0) */
83 #define MSIM_CLIENT_VERSION 697 86 #define MSIM_CLIENT_VERSION 697
84 87
85 /* Language codes from http://www.microsoft.com/globaldev/reference/oslocversion.mspx */ 88 /* Language codes from http://www.microsoft.com/globaldev/reference/oslocversion.mspx */