Slashdot Mirror
MSN Messenger Access To Be Restricted
linuxwrangler writes "According to Infoworld, Microsoft has announced that as of October 15 some third-party software and older versions of MSN Messenger will no longer be able to log in to their Instant Messaging service. Microsoft cited 'security issues', but declined to offer specifics. The company sent an email alert to Messenger users, but users reported thinking the message was a hoax or virus after receiving over a dozen copies of the email."
It's not vendor lock-in if someone else has the key. So yeah, it is a security measure. ;)
The trillian developers are probably working on it as we speak
Microsoft cited 'security issues', but declined to offer specifics.
The "security issue" is, of course, the "leak" of vital advertisement money they would be getting (:
"We are very interested in interoperating with all third parties, there just needs to be a formal agreement,"
Requiring formal agreements could be a sly way to keep open source software out. How would an open source project go about making such an agreement?
The implication that a network is more secure by only allowing MS developed software to access it is bunk. There is no logical reason why restricting clients and implementing security-through-obscurity will reduce anyone's exposure to network security problems.
Well, I guess it would reduce Microsoft's exposure since everyone using the network would have agreed to a Draconian EULA that stripped them of all their rights.
Be assured, this is not about security, it is about control.
I am sure this has less to do with exorbitant fees and more to do with licensing restrictions. Do you really think MS will allow a GPL'd piece of software to access their network after the anti-GPL campaign they have conducted?
MS is stifling interoperability. Just like they have in the past, and just like they will do in the forseeable future.
The guys at Trillian have been managing just fine over the years, working out how the various IM communicate and successfully implementing the protocols. This is just some MS FUD to get people to stop using the likes of Trillian. But never fear, I bet by OCt 15 I'll be logging into MSN via my updated version of Trillian.
"She's a West Texas girl, just like me" - G.W Bush Iraqis
... do you see something like this:
uh huh... ... bullshit!!
(Score: 2, Insightful)
What is it about microsoft articles that cause the average IQ to plummet around here?
In all matters of opinion, our adversaries are insane. -Oscar Wilde
This is pretty typical of Microsoft though, so it isn't really any surprise is it?
[1] Attempt to crack market with new software
[2] Bundle software with OS - make pain in ass to remove
[3] wait for large user base to build
[4] close off to other vendors (you are here)
[5] wait for competition to die off
[6?] China decides to make it's own impementation =P
It's not a "sly way to keep open source software out"*, it's a not-so-sly way to counter OTHER people getting ad revenue/sales off YOUR network service, among other things.
MSN messenger only really makes money off:
(last two being market-share 'enhancers')...which is pretty much why AOL offers AIM independently too. When a client like Trillian is a)letting people use your service without showing you ads and b)letting users talk to anyone on any network...well, now, you've just shot 2 out of 3 reasons for MSN messenger's free-ness, haven't you?
Not to mention, someone at MSN's sales deparment finally realized "Hmm,, people are making money SELLING a client for our network! Hey! I bet WE can get a piece of that money!" They probably approached Trillian, Trillian probably told them to go screw, and MSN said "hah, watch us pull the plug". So, basically, Trillian etc will be forced to sign an agreement forking over xx% of their [gross/net/whatever] sales, the business world will perhaps do a little more than yawn, and the sun will rise tomorrow...meanwhile, Instant Messaging Planet will generate a dozen news stories and at least one conference over the whole thing ;-)
* let's drop the persecution complex, for crissakes- companies do things for one reason, and one reason only- to MAKE MONEY, not join The Man in fucking open source over.
Please help metamoderate.
All of which were retractions to prior bulletins because of flaws in the patches for the flaws, like I got?
MS02-040 REVISED: Microsoft Security Bulletin MS02-040: Unchecked Buffer in MDAC Function Could Enable System (Q326573)
MS03-030 REVISED: Microsoft Security Bulletin MS03-030: Unchecked Buffer in DirectX Could Enable System Compromise (Q819696)
MS03-029 REVISED: Microsoft Security Bulletin MS03-029: Flaw in Windows Function Could Allow Denial of Service (Q823803)
And people wonder why I won't install a MS Patch on a production system without thorough testing.
They have a proven (and documented) track record of breaking things, both intentionally (DR-DOS) and unintentionally. They have been convicted of anticompetetive practices.
And they expect me to believe that this move is for 'Security'? Sounds to me more like the security of their wallets.
You can have it fast, accurate, or pretty. Pick any 2.
One issue with fragmentation is that metcalfes law works in reverse: exponential loss of value.
If a network is split in two, the value of each network is (.5)^2, or a quarter of the value were the network to be united.
Even though there are now two separate networks, the total value is half what it would otherwise be.