On Tue, 2010-10-05 at 13:09 -0700, John Hardin wrote:
> On Tue, 5 Oct 2010, Michael Scheidell wrote:
> > AWL is NOT an 'auto whitelist'. and is not used by default configs anymore.
> > instead of including the massive volume of documentation on what AWL is and
> > is not, just google.
>
> We _really_ need to change that rule's description...
Uhm, while I would never argue that naming to be unfortunate in
hindsight, despite most of the time actually matching its stated goal...
I blame this one on Alex (the otherwise anonymous $mysqlstudent). He's
been around long enough, by far, to know about this. Just simply and
occasionally glimpsing threads on this list should have told him.
I mean, for once, use this mailing list as a source of wisdom. Most of
us can learn from others' experience. Being subscribed to a mailing list
is not a post-only-if-question medium, but one to read. It's not a
fucking substitute for an easy google search, either.
Or our very own wiki. Ask it for "awl". Can you say AwlWrongWay!?
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
