From: frederik@ofb.net
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org, joseph@codesourcery.com
Subject: Re: bugs not showing up on Google
Date: Thu, 06 Sep 2018 06:01:00 -0000 [thread overview]
Message-ID: <20180906060117.GJ27595@ofb.net> (raw)
In-Reply-To: <20180829234015.GC2249929@elastic.org>
> > joseph@codesourcery.com suggested that I email you about my
> > observation that most of your bugs are not showing up on Google.
> > [...]
>
> I don't know about "most"; undoubtedly many appear and some do not.
> It may be relevant that we have had to throttle googlebot from
> full access to the sourceware web servers because it was repeatedly
> found ignoring robots.txt and saturating the server with traffic.
> So we have reluctantly slowed its access down. I expect it to
> get around to all the bugzilla entries over time, just maybe not as
> fast as you expect.
Thanks Frank for your reply. The entry I was looking at was over a
year old. I don't know what you mean by "over time" but I would
consider that too long. Also I don't think it would take that long for
even a throttled Googlebot to crawl your site.
I'm not sure how a crawler is supposed to see all the bugs, is there a
way of listing them all without going through a search form?
Apparently there are ways to enforce robots.txt using mod_rewrite: as
long as Googlebot doesn't change its user agent, I think you can more
or less easily prevent it from accessing a given URL:
https://perishablepress.com/eight-ways-to-blacklist-with-apaches-mod_rewrite/comment-page-4/
That seems easier to me than QoS tuning.
Even better would be if we could report bugs to Google but ... yeah.
For me it's always been a Wall of Silence.
By the way, I couldn't find a public archive of this mailing list,
should we be discussing this on Bugzilla in case other Bugzilla
maintainers want to benefit from your experience?
https://sourceware.org/bugzilla/show_bug.cgi?id=23581
Maybe I can paste these messages into a comment on that bug and then
add overseers to the Cc list? Or am I tripping and no one cares?
Thanks,
Frederick
next prev parent reply other threads:[~2018-09-06 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 17:34 frederik
2018-08-29 23:40 ` Frank Ch. Eigler
2018-09-06 6:01 ` frederik [this message]
2018-09-06 19:22 ` Christopher Faylor
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=20180906060117.GJ27595@ofb.net \
--to=frederik@ofb.net \
--cc=fche@elastic.org \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).