From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Google privacy changes
Date: Fri, 27 Jan 2012 10:14:48 -0600 [thread overview]
Message-ID: <CAEH5T2MYh0ui6QfzeQV4GrRhZ1P8FLW8CxUbDKYDGLwTaZO26Q@mail.gmail.com> (raw)
In-Reply-To: <20120127164835.f1e12ba8.v_2e@ukr.net>
On Fri, Jan 27, 2012 at 8:48 AM, <v_2e@ukr.net> wrote:
> Hello!
>
> On Thu, 26 Jan 2012 01:16:01 -0600
> Dale <rdalek1967@gmail.com> wrote:
>
>> Does anyone have a better search tool? I don't like Yahoo either. I
>> do like froogle so that would be a bonus. You know, shopping tool.
>>
>> Thoughts? Suggestions?
>>
> What about Yandex? It provides a search tool and a mail box with POP3
> and IMAP protocols support free of charge. And by the way, they say
> that the mailbox size is also indefinite (well, at least
> theoretically :) ).
I'll add a vote of support for Yandex. It usually has good results,
though it really depends on what you are searching for. I did some
test queries asking random linux questions and the link containing the
solution was usually higher in the list on Yandex when compared to
Google. Comparing local shopping prices in the US, use Google
instead...
Based on my web server logs, the bots which check the most often are:
1. Baidu
2. MJ12
3. Gootkit auto-rooter
4. Bing
5. Yandex
6. Yobao
7. Google
8. ZmEu
3 and 8 are bots trying exploits, 2 is not a search engine, 1 and 6
are not available in English, 4 is Microsoft, and 7 is excluded for
the present conversation. So, Yandex seems a good choice. In fact, the
only remaining choice. :)
BTW, the Baidu spider hits my site more than all of the others combined...
next prev parent reply other threads:[~2012-01-27 16:16 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 7:16 [gentoo-user] Google privacy changes Dale
2012-01-26 8:47 ` J. Roeleveld
2012-01-26 8:48 ` Michael Mathurin
2012-01-26 10:07 ` Mick
2012-01-26 11:33 ` Neil Bothwick
2012-01-26 12:56 ` Mick
2012-01-26 13:50 ` Neil Bothwick
2012-01-26 14:05 ` Michael Hampicke
2012-01-26 14:10 ` Michael Mol
2012-01-26 14:16 ` Dale
2012-01-26 14:34 ` Michael Mol
2012-01-26 16:04 ` Frank Steinmetzger
2012-01-26 16:14 ` Michael Mol
2012-01-27 0:38 ` William Kenworthy
2012-01-27 1:49 ` Michael Mol
2012-01-27 8:47 ` Neil Bothwick
2012-01-26 16:20 ` Mick
2012-01-26 18:36 ` Mike Edenfield
2012-01-26 16:12 ` Paul Hartman
2012-01-26 16:18 ` Michael Mol
2012-01-26 16:18 ` Michael Hampicke
2012-01-26 16:24 ` James Broadhead
2012-01-27 6:41 ` Graham Murray
2012-01-27 14:53 ` Michael Mol
2012-01-26 20:45 ` Daniel da Veiga
2012-01-26 15:13 ` Neil Bothwick
2012-01-26 15:23 ` Michael Mol
2012-01-26 14:12 ` Mick
2012-01-26 15:12 ` Neil Bothwick
2012-01-26 21:29 ` Alan McKinnon
2012-01-27 0:48 ` Peter Humphrey
2012-01-27 12:21 ` Mick
2012-01-27 12:31 ` Neil Bothwick
2012-01-27 12:59 ` Mick
2012-01-27 13:13 ` Neil Bothwick
2012-01-27 13:24 ` Alan McKinnon
2012-01-26 21:47 ` Michael Hampicke
2012-01-26 23:02 ` Neil Bothwick
2012-01-26 18:09 ` Florian Philipp
2012-01-26 19:30 ` Mick
2012-01-26 19:52 ` Michael Mol
2012-01-26 20:06 ` Paul Hartman
2012-01-26 20:57 ` Neil Bothwick
2012-01-26 8:58 ` Walter Dnes
2012-01-26 12:36 ` Timo Briddigkeit
2012-01-26 13:07 ` John J. Foster
2012-01-26 13:59 ` Dale
2012-01-26 15:22 ` John J. Foster
2012-01-26 15:28 ` John J. Foster
2012-01-26 16:08 ` Frank Steinmetzger
2012-01-27 0:08 ` Dale
2012-01-26 16:38 ` Paul Hartman
2012-01-26 17:11 ` Lorenzo Bandieri
2012-01-26 17:35 ` Mick
2012-01-26 17:38 ` Paul Hartman
2012-01-27 6:57 ` Dale
2012-01-27 18:49 ` Florian Philipp
2012-01-27 14:48 ` v_2e
2012-01-27 16:14 ` Paul Hartman [this message]
2012-02-08 8:55 ` Pandu Poluan
2012-02-08 15:46 ` Paul Hartman
2012-02-08 15:53 ` Michael Mol
2012-02-08 17:17 ` Pandu Poluan
2012-02-08 18:28 ` Michael Mol
2012-01-29 14:35 ` Volker Armin Hemmann
2012-01-29 19:12 ` Dale
2012-01-29 19:47 ` Mick
2012-01-29 23:57 ` Chris Walters
2012-02-08 8:01 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEH5T2MYh0ui6QfzeQV4GrRhZ1P8FLW8CxUbDKYDGLwTaZO26Q@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox