Windows Live Mesh (Beta). I give this app and Microsoft a rank of EPIC FUCKING FAIL. Two big thumbs down.Why?
2 reasons.
The first is trivial...I have a widescreen monitor (20.1") and a resolution of 1680x1050 and I connected to my prototype testing rig (I was testing the Mesh Remote Desktop ability) to give this app a spin. That resolution is maxed at 1024x768. This was okay because according to the spec sheets, this is the minimum resolution required. Or so I thought it would be okay...
It was not. Not even close actually. Even after toying with the display settings once I connected, I maximized the screen and used Full Screen capabilities, the mouse pointer from the server side (my side) was NOT CENTERED. What does that mean for performance? Well, if you expect to click an icon, you can't. The mouse pointer on MY side appeared to be hovering directly above the icon on the client side (prototype rig), but each time I tried to click or right click, I got the context menu one would see if the right clicked the Desktop screen.
So I looked back towards my client side, and as I moved the pointer I navigated it on my side to hover over an icon but on the client end, the mouse was actually an inch or more to the left of where it appeared to be on my end. That just meant that, in order for me to right click this icon I wanted, my mouse pointer on MY side had to be an inch or better to the right of what I saw on screen for it to work properly and align to what the client would see.
UNACCEPTABLE.
What I see on MY screen should be what I see on the client end, even at a diminished resolution. To have to make adjustments like navigating over an inch or more to the right for everything I wanted to click on is just absurd and totally unacceptable to me. Microsoft got a FAIL from me for this alone.
Then we get to the second item, and THIS had my head spinning. This item is NOT trivial in any way, and is in fact a HUGE liability and security risk to anyone using this product.
In order to use "Live Mesh", one has to have a Windows Live ID, so let's say a Hotmail address or .Live address. You access the Mesh site and download their software and install it. You sign in, and the app is ready to go once the device has been added to your "Mesh". I installed this app on my system and the prototype and added the 2 systems to my "Mesh" and vice versa. Now here's where it gets tricky...
I was logged in and signed on to both systems. I first tried to access the prototype. I connected and as they said it would, there was a dialog on the screen that said "Allow" or "Deny" the remote connection request.
Now pay attention to this part...
If the client end does not select one of the items, Allow or Deny within 30 seconds...IT AUTO-CONNECTS ANYWAYS. Yes, that's what I said...if the client doesn't explicitly Deny the connection, Mesh will connect itself after 30 seconds. Microsoft is aware of this as they have it listed as a "Feature". A FUCKING "FEATURE"?! Okay, so we tried the connection from the prototype to my system. That worked too and auto-connected as did the first attempt. From a diminished resolution (remember, prototype is 1024x768 only) to a higher resolution, this made for one Hell of a challenge to actually accomplish anything...but at least what I saw on that screen was what I was clicking on the client end, which was now MY system.
But then I got curious...
I figured with such a huge vulnerability as the auto-connect "feature"...what happens if I try to connect and the system is ON, but not logged in to Live, and Mesh is actually OFF?
I found out what happens...and damn near screamed.
It still logs you on automatically.
Yes way.
My Mesh was signed out, and so was my Windows Live account on the prototype. In effect, this means that my computer may be indeed on, but I'm not actually signed on or using any Live applications.
To Mesh, that doesn't matter.
It connected me anyways.
So I immediately removed that piece of shit application knowing what a huge risk it would pose to leave it on my systems. I then sent Microsoft a scathing feedback submission telling them about my experiment. I can't imagine anyone with an ounce of sanity allowing this piece of garbage to be installed on their systems at home or especially at WORK, just knowing that all it takes is the computer to be ON and anyone can access it at anytime (as long as it's in their "Mesh"), because there's no requirement for Mesh to be active or for you to be signed in to a Live account...and let's not forget the auto-connect "feature".
I gave Microsoft an EPIC FUCKING FAIL for that piece of nonsense right there.
I understand that this is Beta, but for the love of Mike...who in their right mind would see NOT being required to have Mesh running or to be logged in to a Live account, and an auto-CONNECT "feature" as a GOOD thing?! I know I certainly don't, and would never. You're just asking for trouble at that point. Making it a requirement to have Mesh ON or to be logged into a Live account would be a good place to start. Turning the auto-CONNECT in 30 seconds to a auto-DENY in 30 seconds would be the next step. If I'm not physically there to Allow or Deny you access to my system, it should auto-DENY you until I get there.
What the fuck was Microsoft thinkin' callin' that shit a "feature"?
So yea, if you're thinking about using this lame ass app, USE IT AT YOUR OWN RISK.
All I'm sayin'...
No comments:
Post a Comment