On Tue, 2014-09-09 at 11:10 +0200, Antony Stone wrote:
> On Tuesday 09 September 2014 at 11:04:04 (EU time), Martin Gregorie wrote:
>
> > I use Fedora, which is roughly equivalent to Debian unstable, i.e. fairly
> > cutting edge as its the next step back toward stability from 'testing'.
>
> Hm, t
On Tuesday 09 September 2014 at 11:04:04 (EU time), Martin Gregorie wrote:
> I use Fedora, which is roughly equivalent to Debian unstable, i.e. fairly
> cutting edge as its the next step back toward stability from 'testing'.
Hm, that's not quite the right way round - "testing" is the step in betw
On Tue, 2014-09-09 at 10:41 +0200, Axb wrote:
> On 09/09/2014 10:27 AM, Martin Gregorie wrote:
> > On Mon, 2014-09-08 at 23:05 -0600, Amir Caspi wrote:
> >> An automated method would prevent a number of problems, and since the
> >> allowed TLDs are evolving, I think it makes the most sense. I can't
Am 09.09.2014 um 03:45 schrieb Karsten Bräckelmann:
> This incidence is part of the initial round of IANA accepting generic
> TLDs. There's hundreds in this wave, and some are abused early. This is
> moonshine registration, nothing like new TLDs being accepted in the
> coming years.
>
> Or is it?
On 09/09/2014 10:27 AM, Martin Gregorie wrote:
On Mon, 2014-09-08 at 23:05 -0600, Amir Caspi wrote:
An automated method would prevent a number of problems, and since the
allowed TLDs are evolving, I think it makes the most sense. I can't
speak to a specific implementation, but -something- automa
On Mon, 2014-09-08 at 23:05 -0600, Amir Caspi wrote:
> An automated method would prevent a number of problems, and since the
> allowed TLDs are evolving, I think it makes the most sense. I can't
> speak to a specific implementation, but -something- automated...
>
Same here: I pick up new SA versio
On Tue, Sep 09, 2014 at 07:10:34AM +0200, Axb wrote:
> On 09/09/2014 07:04 AM, Henrik K wrote:
> >On Tue, Sep 09, 2014 at 03:45:33AM +0200, Karsten Bräckelmann wrote:
> >>
> >>There is one down side: A new dependency on Regexp::List [1]. The RE
> >>pre-compile one-time upstart penalty should be neg
On 09/09/2014 07:04 AM, Henrik K wrote:
On Tue, Sep 09, 2014 at 03:45:33AM +0200, Karsten Bräckelmann wrote:
There is one down side: A new dependency on Regexp::List [1]. The RE
pre-compile one-time upstart penalty should be negligible.
[1] Well, or a really, really f*cking ugly option that ta
On Sep 8, 2014, at 7:45 PM, Karsten Bräckelmann wrote:
>
> Opinions? Discussion in here, or should I move this to dev?
Given that TLDs can and do change on a timescale more frequent than many people
update their version of SA (myself included), I would vote for a method that
treats this as a c
On Tue, Sep 09, 2014 at 03:45:33AM +0200, Karsten Bräckelmann wrote:
>
> There is one down side: A new dependency on Regexp::List [1]. The RE
> pre-compile one-time upstart penalty should be negligible.
>
> [1] Well, or a really, really f*cking ugly option that takes a
> pre-optimzed qr// blo
On 9. sep. 2014 04.29.55 Karsten Bräckelmann wrote:
Apart from that nitpick, I understand you would be in favor of a Valid
TLD option, rather than hard-coded. Noted.
Perl programmer make there signature in perl code
Well i still thinking about url reputation, but since nearly all kind of
si
>>embedded in the rules.
> ^
>Code, not rules. Which basically is the issue here...
Just read what I *mean* and not what I type. ;-)
--
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com
"...Life is not a journey to the grave with the intention of arriving
safely in one pretty
On Mon, 2014-09-08 at 21:45 -0500, Dave Pooser wrote:
> On 9/8/14 8:45 PM, "Karsten Bräckelmann" wrote:
>
> >There is one down side: A new dependency on Regexp::List [1]. The RE
> >pre-compile one-time upstart penalty should be negligible.
> >
> >[1] Well, or a really, really f*cking ugly option
, this is not actually a 3.3.x issue. It's the same with 3.4.0. Yes,
> >> that is a *recent* TLD addition... *sigh*
> >
> > Unlike the util_rb_[23]tld options, the set of valid TLDs is actually
> > hard-coded. It would not be a problem to make that an option, too.
> &
On 9/8/14 8:45 PM, "Karsten Bräckelmann" wrote:
>There is one down side: A new dependency on Regexp::List [1]. The RE
>pre-compile one-time upstart penalty should be negligible.
>
>[1] Well, or a really, really f*cking ugly option that takes a
>pre-optimzed qr// blob containing the VALID_TLDS
just recently. Of course I was conveniently
>> using a trunk checkout for testing and kind of shrugged off that TLD in
>> question.
>>
>> FWIW, this is not actually a 3.3.x issue. It's the same with 3.4.0. Yes,
>> that is a *recent* TLD addition... *sigh*
>
On Mon, 2014-09-08 at 22:15 -0400, Daniel Staal wrote:
> --As of September 9, 2014 3:45:33 AM +0200, Karsten Bräckelmann is alleged
> to have said:
>
> > This incidence is part of the initial round of IANA accepting generic
> > TLDs. There's hundreds in this wave, and some are abused early. This
--As of September 9, 2014 3:45:33 AM +0200, Karsten Bräckelmann is alleged
to have said:
This incidence is part of the initial round of IANA accepting generic
TLDs. There's hundreds in this wave, and some are abused early. This is
moonshine registration, nothing like new TLDs being accepted in
ng and kind of shrugged off that TLD in
> question.
>
> FWIW, this is not actually a 3.3.x issue. It's the same with 3.4.0. Yes,
> that is a *recent* TLD addition... *sigh*
Unlike the util_rb_[23]tld options, the set of valid TLDs is actually
hard-coded. It would not be a prob
19 matches
Mail list logo
