On Tue, Jan 24, 2012 at 7:55 PM, C Anthony Risinger <[email protected]> wrote:
> On Jan 24, 2012 12:38 AM, "lkcl luke" <[email protected]> wrote:
>> On Tue, Jan 24, 2012 at 12:30 AM, Peter Bittner <[email protected]>
>> wrote:
>> >
>> > It should be something like: (all in one line)
>> >  RewriteRule
>> >  ^pyjs.org/pyjamaslamson/librelist/app/data/archive/([a-z])/([0-9]{4})/([0-9]{2})/([0-9]{2})/queue/new/([0-9a-zA-Z.]+)$
>> >  http://lists.pyjs.org/mail/#$1:$2:$3:$4:$5 [R]
>>
>>  anthony, you wanna put that in?  i can't bring myself to look at it :)
>
> Yeah I can set this up shortly; however as is this will redirect google
> itself and any other engines -- IOW the content will stop being indexed.

 ahh argh, well spotted.

> There is a protocol to inform google of the relation between dynamic Ajax
> pages and their static counterparts ... ill have to look it up again, but we
> may want to handle it a bit different.

 ah... it involves putting a "!" immediately after that "#".

> Redirects should probably be 301s as well (`R` defaults to 302)
>
> There is another option, albeit a bit hackier, and that's to use an Apache
> module to dynamically wrap the plain txt message with a template containing
> either a JavaScript/meta redirect, or a simple button that says "click to
> view in app reader"
>
> ... a bit trickier, but I think the last is the best.  Google and friends
> don't like being tricked (cloaking IIRC in SEO world == bad points).

 *sigh* what i've been forced to do is to put comments in the HTML
which say, to the effect of "google etc, you are morons for not coming
up with a decent solution to AJAX, so we are forced to deploy these
tricks".

 if the site actually gets reviewed by a human the gist is that they
should understand what the hell is going on.

 but, this is a free software project: it's not being designed to
steal money from google in the name of profit-maximisation, so all in
all using such tricks - because they're simple and effective - is ok.

l.

Reply via email to