Where, Oh Where Did myImager Go ?
There has been much ado about myIMager and the Computer mime that shows when WebTV users click on their link. Let's take a few moments to analyze the situation and determine the cause.
I was priviledged to be in a chat room with a certain MSNTV employee who convinced me that the problem is totally MSNTV's shortcomings. Many folks in that chat session disagree, because they do not understand how the net works, nor how the employee is bound by his conditions of employment.
Here are links to prove the point:
http://myImager.com shows computer mime when queried through MSNTV routers. Here is what I saw with my PM Plus unit using 2.6.1 client build.
Screen shot
Copy and paste text
When accessed by a PC browser or WebTV browser that is going through proxify.com or other proxy servers, other than MSNTV, the page looks like this:
As seen before myImager's latest update.
As seen after myImager's latest update.
The pages shown are exact copies of the code for myImager's. They are not working copies, because the support files are not on this server, but they prove that myImager is
at least viewable with WebTV IF the browser is being shown the proper url as queried.
Now, back to the chat session:
When confronted with the statement that the problem is with MSNTV, the employee stated:
"The official cause is not MSNTV's. The ball has been in their(myImager.com)court for over a month".
READ: The official versus the true and obvious cause. I can only state the "official" because I want to keep my job. We dropped the ball and our story is that it rolled over to myImager's side of the court.
When asked why it shows on PCs just fine, he stated he was getting an error message on his PC. I stated that I was getting no error messages, why is that? He responded with
"Because your ISP is not 240.209.xxx.xx".
Is not that enlightening? We have a MSNTV employeee claiming site incompatability when he is not even trying to access the site through a non-MSNTV server on his PC! Well, not exactly. What he was doing was double speak to alert those intelligent observers to see the obvious.
When quizzed about the error message, he responded that the site was sending some type of streaming code, and that it was the only site on the internet doing that. I suppose he checked all the umpteen gazillion sites on the net to determine that. Of course not. He was just bringing attention to the MSNTV server again. If myImager.com were sending out a type of streaming code, my MSIE 6.0 browser would be opening it on one of the several media players I have. It is opening as normal html, as it would with WebTV units; IF they were actually being shown the proper IP when queried through the MSNTV servers.
The problem is obvious. MSNTV has router problems and will not correct them for whatever reason. If you want to use myImager, you will just have to take steps to put MSNTV routers out of the loop.
Still not convinced? Take a look at my links again. IF you were seeing myImager.com through the MSNTV server, you would see it exactly as my copy of their index page. Does it look the same? View the source code through my tool or any other source code viewer and see if you get that computer mime. I bet you will see normal html and javascript.
Until next time, blessings to all.
