Disable Skype integration in Outlook.com and SkyDrive

skypecall_cropped.png

A little over nine months ago, Microsoft rolled out Skype for Outlook.com. This new integration allows users to instant message, make phone calls and even send and receive video -- right from the web browser. It sounds great, but as my colleague Paul Thurrott pointed out then, it comes with a crippling incoming call notification that won't stop ringing after you answer the call with one of the many other applications or devices ringing.

I thought abandoning Outlook.com would be the cure, but Microsoft rolled this integration into SkyDrive too.

Determined to fix this, I ran Outlook.com through Fiddler and noticed Skype code was pulled down and initialized asynchronously from scripts hosted on skypewebexperience.live.com. I thought of various solutions involving DOM manipulation and code injection to unhook Skype, but opted for a simpler brute-force approach: I just pointed the sub-domain to 127.0.0.1 via the HOSTS file (effectively blocking it).

And aside from some minor scripting errors that appear in the browser console, it worked. It even worked in SkyDrive.

Good riddance.

Step-by-step instructions:

  1. Open Notepad as an administrator
  2. Open the file \Windows\System32\Drivers\Etc\Hosts
  3. At the end of the file, add 127.0.0.1 skypewebexperience.live.com and save.
  4. Close Notepad and restart SkyDrive/Outlook.com browser instances.

PSA: Wireless display (Miracast) support is broken on the Surface Pro [now fixed]

With the release of the Windows 8.1 GA rollup (KB2883200), Microsoft seems to have inadvertently broken wireless display (Miracast) support on the Surface Pro.

Affected users will have trouble discovering Miracast capable devices, such as the NETGEAR Push2TV and ActionTec ScreenBeam.

Fix: New Marvell AVASTAR drivers (14.69.24044.150) are available in, funny enough, the Surface Pro 2 driver and firmware pack. They apply to the Surface Pro as well. I'm told these will eventually be pushed out via WU as well. [added 10/25/2013]

It's not clear where the fault lies, but I suspect we'll be seeing updated wireless drivers (Marvell AVASTAR 350N) in the very near future.

Stay tuned. 

For more information on Miracast support in Windows 8.1, check out my previous article

searching_for_devices.png

Surface Pro gets new wireless drivers for Windows 8.1

Marvell_Avastar_88W8797_SoC.jpg

A keen-eyed buddy of mine, George Roberts, tweeted this morning about new Marvel 88W8797 drivers on Windows Update today. The newer drivers (14.69.24040.136) feature full Windows 8.1 (post-preview) support (i.e. NDIS 6.4) and the required high throughput/low latency improvements needed to properly support scenarios such as wireless display and Skype.

Speaking of wireless display -- some of you may have noticed the feature stopped working on Surface Pro after upgrading from Windows 8.1 Preview to RTM. Well, it's time to turn that frown upside down because after installing these drivers, it's back.

Thanks for the heads up George! 

Outlook.com supports simpler "+" email aliases too

outlook.png

Outlook.com's email aliases are handy extensions of your core email account and can be used for outbound account consolidation or inbound mail categorization. Sounds complicated and hard to set up, but it's not. Paul Thurrott has some tips on setting it up and answers any questions you may have.

But if you're looking to create a cheap and easy inbound-only alias, or want an alias tied to your custom domain name, here's a quick tip: Outlook.com also supports Gmail's "+" aliasing.

For example, mail sent to rafael+pogs@withinwindows.com lands in my inbox at rafael@withinwindows.com without any additional configuration. It just works. And you can of course set up rules to put these emails into separate folders or delete on sight. (You can replace everything after the + with anything you'd like, as long as it's well formed.)

Neat!

6tag leaks your account data, stores your private videos

6tag_header.png

Windows Phone developer Rudy Huyn released his unofficial Instagram clone app called 6tag today. And while I would love to take this moment to clear up misconceptions about how the app works and Huyn's involvement (or lack thereof) with Instagram, I must defer to another day. That's because I must, instead, share some important privacy concerns uncovered by Windows Phone developer Travis La Marr this morning.

6tag sends account data in the clear

To support video uploads, 6tag emulates the way Instagram's official apps work. That is, video is uploaded from the device to intermediate servers for transcoding into a compatible format and size, one step before Instagram. But where 6tag differs is that it sends your private account data -- for example, your username and authentication tokens -- in the clear, along with your video, to a black box server in France (presumably under the author's control) in preparation for a future app update. That means, in theory, a determined individual at a Starbucks armed with a sniffer could take over your Instagram account easy peasy.

Update 2 8/22 @ 4:22am PST:  Rudy, via Twitter, has indicated cookies will now be encrypted with a "512-bit key" in a future update.

But wait, there's more... 

6tag servers keep a copy of your public and private videos, for an unspecified amount of time

6tag's transcoding servers understandably keep uploaded video around for a little bit, giving the phone app time to grab a copy. What's concerning, however, is that uploaded video never seems to get deleted. For example, here's a permalink to a video I published on Instagram hours ago. And here's a video Travis published over a week ago. Yikes.

Update 1 8/22 @ 3:46am PST: Rudy, via Twitter, has confirmed that his server does not remove videos after publishing to Instagram, instead relying on an undocumented 48 hour retention policy. When asked about Travis' week old video, he noted that video was uploaded via the beta, implying they're special, and that beta videos will be wiped "in less than 48h". Travis' video went dark soon after.

6tag doesn't have a privacy policy

Against Windows Phone App Certification Policy 2.8, 6tag does not come bundled with a privacy policy, or at least one I could find. This means users have no clue what data is sent to Instagram or black box servers in France, nor an understanding of how private user data is handled, protected, or destroyed. How this got through Windows Phone Store testing is beyond me.

 Update 3 8/23 @ 3:40pm PST:  A new privacy policy is up.

Call to action: Upgrade to 1.0.1.0

 

This is a "FAST PUBLISH" article. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time. 

Full disclosure: I was compensated as part of an Instagram API reverse engineering effort for the developer of Instance, a competing app in the Windows Phone Store. This was a one time deal. I do not receive compensation based on the success or failure of Instance, nor care about Instagram in general.