<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6619.12">
<TITLE>All your base are belong -- uh, waitaminute, we didn't really mean that...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><B><FONT FACE="Courier New">From another forum, I got "diverted" to reading about Google's new browser called "Chrome"</FONT></B>
</P>
<P><B><FONT FACE="Courier New">[uhhh, isn't that the underlying tech for firefox? Apparently not...]</FONT></B>
</P>
<P><B><FONT FACE="Courier New">Seems there was a slip-up in legal in which the "standard EULA" for their "services" [gmail, picassa, etc.] were included in the EULA for the browser, and people actually /read/ the EULA and called Google on the carpet for it -- 24 hours later that section of the EULA was retracted [and retroactively, so those millions of windows users who clicked-without-really-reading-it are covered too]</FONT></B></P>
<P><B><FONT FACE="Courier New">How do I know this is limited to "windows users who..."? Well, for one the Mac and Linux ports aren't ready yet :)</FONT></B>
</P>
<P><B><FONT FACE="Courier New">But it is released under a [BSD] open source license, and there are some reports already in about it working semi-natively under "wine" [but since wine's dlls for SSL are "just stubs", "</FONT></B><A HREF="https://"><B><U><FONT COLOR="#0000FF" FACE="Courier New">https://</FONT></U></B></A><B><FONT FACE="Courier New">" addresses don't work]</FONT></B></P>
<P><B><FONT FACE="Courier New">But hey, it's still a week until our general meeting -- perhaps by then the port will be out and someone from our group will have installed it and put it through a few paces...</FONT></B></P>
<BR>
</BODY>
</HTML>