AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2008.07.28 08:49 "[Tiff] CVS access", by Mateusz Łoskot
2008.07.28 13:01 "[Fwd: Re: [Tiff] CVS access]", by Edward Lam
2008.07.28 14:02 "Re: [Tiff] CVS access", by Mateusz Loskot
2008.07.28 23:17 "Re: [Tiff] CVS access", by Ryan Schmidt
2008.07.28 23:57 "Re: [Tiff] CVS access", by Frank Warmerdam
2008.07.29 16:37 "Re: [Tiff] CVS access", by Gary McGath
2008.07.29 17:43 "Re: [Tiff] CVS access", by Graeme Gill
2008.07.29 20:17 "Re: [Tiff] CVS access", by Gene Amtower
2008.07.29 21:01 "Re: [Tiff] CVS access", by Bob Friesenhahn
2008.07.29 22:04 "Re: [Tiff] CVS access", by Gene Amtower
2008.07.30 09:32 "Re: [Tiff] CVS access", by Andrew Brooks
2008.08.11 20:55 "Re: [Tiff] windows 64 bit build", by Bob Friesenhahn
2008.08.11 19:35 "Re: [Tiff] windows 64 bit build", by Mikhail Kruk
2008.08.11 17:57 "[Tiff] windows 64 bit build", by Mikhail Kruk
2008.08.11 19:29 "Re: [Tiff] windows 64 bit build", by Bob Friesenhahn
2008.08.12 00:41 "Re: [Tiff] windows 64 bit build", by Edward Lam
2008.08.11 20:03 "Re: [Tiff] windows 64 bit build", by Edward Lam
2008.08.11 20:51 "Re: [Tiff] windows 64 bit build", by Bob Friesenhahn
2008.08.12 00:36 "Re: [Tiff] windows 64 bit build", by Edward Lam
2008.08.12 02:44 "Re: [Tiff] windows 64 bit build", by Bob Friesenhahn
2008.08.12 03:53 "Re: [Tiff] windows 64 bit build", by Edward Lam
2008.08.12 04:04 "Re: [Tiff] windows 64 bit build", by Mikhail Kruk
2008.08.12 12:54 "Re: [Tiff] windows 64 bit build", by Edward Lam
2008.08.12 04:47 "Re: [Tiff] windows 64 bit build", by Bob Friesenhahn
2008.08.12 13:04 "Re: [Tiff] windows 64 bit build", by Edward Lam
2008.08.13 04:23 "[Tiff] tif_win32.c patch proposal (was: windows 64 bit build)", by Edward Lam
2008.08.13 05:32 "[Tiff] Re: tif_win32.c patch proposal (was: windows 64 bit build)", by Bob Friesenhahn
2008.09.04 14:12 "[Tiff] Re: tif_win32.c patch proposal", by Edward Lam

2008.07.29 20:17 "Re: [Tiff] CVS access", by Gene Amtower

On Wed, 2008-07-30 at 03:43 +1000, Graeme Gill wrote:

Given it's bogus, it's hard to understand why so many links point at it. Is the google ranking being manipulated?

>From what I know about google, I highly doubt that there is any intentional ranking manipulation. However, it seems plausible that a fair number of websites for "important" development projects may reference the incorrect website due to old information, causing google to rank the old site very highly due to lots of referencing sites. This is one important measure google uses to ascertain the importance of a website.

As a case in point, I did a google search looking for websites that point to the libtiff-dot-org website domain, and I came up with one big one at the PHP documentation website. I submitted a request for correction in the PHP documentation to the PHP documentation mailing list, but I suspect this is NOT an isolated case. This is one important limitation of the web - it lives forever unless we "wipe" the history clean from time to time.

Please note: Another important consideration is that google's indexing bots certainly review the content of postings on mailing list archives, so every mailing list posting that includes the address of that incorrect site (libtiff-dot-org) is only making the problem worse! Every post with this info raises the importance of that darned site one more notch to the google ranking engine. Can (and should) we clean out the archives for this libtiff mailing list of this bogus address to avoid causing the problem ourselves, maybe replacing it with the coded address as I've done above to avoid increasing its rank even further?

Gene