I'm forced to agree with this Slashdot poster. The use of a red X in this context will confuse users about perfectly correct and properly
working websites, particularly legacy sites that carry no practical risks and contain widely referenced information, but that cannot be
upgraded to SSL in a practical manner. The most likely outcome will be users learning to ignore such warnings completely because they will be so widely present and widely viewed as "crying wolf." It is also likely that many sites will push back against Google on this by posting explicit messages on their pages explaining to users that Google is playing Mommy and that nothing is wrong with their sites. It is
perfectly acceptable and reasonable for Google to encourage the use of SSL. However, the approach being discussed is not helpful and is likely to even be counterproductive.
REFERENCE: "When Google Thinks They're Your Mommy" -
http://lauren.vortex.com/archi...
Actually I've been here since the dawn of time. Maybe earlier. But the point is, the Slashdot audience does include a lot of people who are not technical wizards. I'll leave it at that.
I think you may be somewhat overestimating the ability of many users to set up these environments in various cases without specific instructions. I know that when I mentioned that I was happy with this solution (in another venue) I got flooded with people asking for step-by-step instructions. In any case, all I did was note the posting, and I assume that the Slashdot editors have a pretty good sense of what will be useful/interesting to their readership overall, which seems to include a significant number of non-techies these days.
No representation was made that this was earth-shattering news. Rather, a *lot* of people had been asking specifically how to make this work (not everyone is as knowledgeable about this area as some folks seem to think!) and the goal was to provide an approach with specific instructions that would function for people already using Google Voice, or who can obtain Google Voice accounts. This approach also has the advantage of going direct to Google Voice servers, rather than via third parties, which is also a plus (as far as I'm concerned, anyway).
Out here in the West San Fernando Valley (Los Angeles) -- and it can get *very* hot here during the summer -- where AT&T has widely deployed VRAD cabinets (though U-verse is not activated here yet), I've recently noticed another sign of possible overheating problems.
On the side of the VRAD cabinets is apparently a large air intake with
an exposed filter element. On several units I've observed recently, the
filter element first vanished completely, and then was replaced shortly thereafter with what appear to be rather bulky external fan units.
Interesting.
--Lauren--
Greetings. If you do a search on Google for "iraqi prisoner abuse" you'll find plenty of entries. My own blog comes up just fine with its collection.
--Lauren--
Lauren's Blog: http://www.vortex.com/lauren-blog
(Search for "prisoner" on the blog to find the items.)
Slashdot Mirror
I'm forced to agree with this Slashdot poster. The use of a red X in this context will confuse users about perfectly correct and properly working websites, particularly legacy sites that carry no practical risks and contain widely referenced information, but that cannot be upgraded to SSL in a practical manner. The most likely outcome will be users learning to ignore such warnings completely because they will be so widely present and widely viewed as "crying wolf." It is also likely that many sites will push back against Google on this by posting explicit messages on their pages explaining to users that Google is playing Mommy and that nothing is wrong with their sites. It is perfectly acceptable and reasonable for Google to encourage the use of SSL. However, the approach being discussed is not helpful and is likely to even be counterproductive. REFERENCE: "When Google Thinks They're Your Mommy" - http://lauren.vortex.com/archi...
Just out of curiosity, if you're that disdainful of Slashdot's editorial prowess, why do you visit here at all? I mean that as a serious question!
Actually I've been here since the dawn of time. Maybe earlier. But the point is, the Slashdot audience does include a lot of people who are not technical wizards. I'll leave it at that.
I think you may be somewhat overestimating the ability of many users to set up these environments in various cases without specific instructions. I know that when I mentioned that I was happy with this solution (in another venue) I got flooded with people asking for step-by-step instructions. In any case, all I did was note the posting, and I assume that the Slashdot editors have a pretty good sense of what will be useful/interesting to their readership overall, which seems to include a significant number of non-techies these days.
No representation was made that this was earth-shattering news. Rather, a *lot* of people had been asking specifically how to make this work (not everyone is as knowledgeable about this area as some folks seem to think!) and the goal was to provide an approach with specific instructions that would function for people already using Google Voice, or who can obtain Google Voice accounts. This approach also has the advantage of going direct to Google Voice servers, rather than via third parties, which is also a plus (as far as I'm concerned, anyway).
Out here in the West San Fernando Valley (Los Angeles) -- and it can get *very* hot here during the summer -- where AT&T has widely deployed VRAD cabinets (though U-verse is not activated here yet), I've recently noticed another sign of possible overheating problems. On the side of the VRAD cabinets is apparently a large air intake with an exposed filter element. On several units I've observed recently, the filter element first vanished completely, and then was replaced shortly thereafter with what appear to be rather bulky external fan units. Interesting. --Lauren--
Greetings. If you do a search on Google for "iraqi prisoner abuse" you'll find plenty of entries. My own blog comes up just fine with its collection. --Lauren-- Lauren's Blog: http://www.vortex.com/lauren-blog (Search for "prisoner" on the blog to find the items.)