[chef] Re: Re: Re: is it by design tak that the chef list isn't public, or indexed by google?

[Nathan Haneysmith < >]

I've switched over to a javascript obfuscated name protection. Should
stop (some of) the bots, but still be human readable.

Thanks,

Nathan

On Fri, Jul 31, 2009 at 10:34 AM, Thomas
Hartman<
 >
 wrote:
> the ideal thing would be to have an indexed lists, with names
> protected by captcha (as with googlegroups) or simply not available
> (as with mailman, I think).
>
> This will probably sound strident, but I think indexing is important
> enough that I would start the list over if there isn't a way to
> achieve this with sympa... probably googlegroups if it were up to me
>
> On Fri, Jul 31, 2009 at 10:27 AM, Nathan 
> Haneysmith<
 >
>  wrote:
>> The archives are currently public and do not require signing up for the 
>> list.
>>
>> It DOES require accepting a cookie to prevent email address
>> harvesting. This has a side effect of also preventing search engine
>> indexing. I'll take a look at the other protection methods offered by
>> Sympa and see what the best balance is that will allow for the
>> indexing.
>>
>> Thanks!
>>
>> Nathan
>>
>> On Fri, Jul 31, 2009 at 9:58 AM, Thomas
>> Hartman<
 >
>>  wrote:
>>> I sent a colleague a link to the thread of answers to my last
>>> questions, and he couldn't read it without signing up for the mailing
>>> list.
>>>
>>> If this is by design ok, but if it's just an oversight I would
>>> recommend opening the list archives to indexing so the wisdom can
>>> spread.
>>>
>>> --
>>> Thomas Hartman
>>>
>>> Darcs hosting: patch-tag.com
>>> Build a webapp with haskell: happstack.com
>>>
>>
>>
>>
>> --
>> Nathan Haneysmith | www.opscode.com
>> 
 
>>  | 206.508.4799
>>
>> OpsCode Inc
>> 119 1st Avenue S, Suite 100
>> Seattle, WA 98104
>>
>
>
>
> --
> Thomas Hartman
>
> Darcs hosting: patch-tag.com
> Build a webapp with haskell: happstack.com
>



-- 
Nathan Haneysmith | www.opscode.com

 
 | 206.508.4799

OpsCode Inc
119 1st Avenue S, Suite 100
Seattle, WA 98104