quote:
Originally posted by V@no
what they suggested is move received text links into input box, WLM automatically will convert them into clickable links. Theoretically it could work, but IMO it would create more problems then solve annoyance...
indeed, that will open a whole lot more problems and (even bigger) annoyances.
----------
just make a script which detects urls in messages and which has a keyboard shortcut to open the '
last received' url in that conversation and be done with it.
(note: urls can contain many protocols though, http is just one of many. eg: https, ftp, irc, news, etc...)
Or use Spunky's script:
Spunky's reply to Is this issue caused by plus?
----------
quote:
Originally posted by John Scarrow (General Manager - MS Safety Services) on WindowsTeam Blog on November 16, 2010 as a reply to posts
Thanks for the comments on the post. I’m hearing 3 general concerns here that I’d like to address.
Q: Why disabling and why only just now?
1) It’s true that similar attacks have been out there for some time, and we’ve been monitoring them, which is why we introduced the new Link Safety Feature in Windows Live Messenger 2011. However the difference with this particular variant of SLENfBot.AKD, (which is actually hitting several industry IM clients, and not just Windows Live Messenger), is that it is off the charts in terms of scale. We have work going on now to illuminate this particular threat so we can restore hotlinks, but the volume of attacks was too significant to let continue without any remediation. The number of customers that have been impacted on a daily basis is very significant, and every impacted customer leads to many more customers being hit with spam, and chances are, some percentage of those receiving the spam will click the link and expand the attack further.
Q: Users do not like it / Insulting for 'tech savy' users / etc
2) Folks that spend time on this blog are clearly “better than average drivers” and in some cases feel that removing the hot links is more undesirable that the perceived protection of disabling them. Again, we hope this is a short term issue for older versions of Messenger. We’ve heard your feedback loud and clear on the ability to turn off warnings, and are investigating ways to make this possible in the future.
Q: It is just an attempt to let people update
3) Because we work hard to make our software more and more secure with every release, from a security standpoint we always hope that users will follow us as we release new versions of our software. However, I want to make it very clear that this security response is absolutely not an attempt to nudge folks to upgrade. We understand and respect that with any change to such an ubiquitous IM client as Messenger there will always be changes that some folks don’t like and/or may not be able to take advantage of due to OS versions, etc. We’ll continue to innovate both in features and security and look forward to broader adoption over time, as you see fit.
questions/comments added by me for clarification
/ 
