Re: Issue 2: Use of the term "3rd-party"

The tool I use (in KDE) uses regex. That really works, but may be too 
powerful to be politically acceptable as a standard. 


On Thursday 12 April 2012 22:12:15 Andy Zeigler wrote:
> Hey Rob,
> Great point. I haven't seen very many implementations that use IP address
> "in the wild", but the list format can accommodate IP addresses. There is
> no special affordance in the syntax like there is for domain names (i.e.
> allow/block by subnet mask), but regular string matching rules (+-) can
> block IPs.
> At a minimum, the spec should clearly call out the expected behavior with
> IP addresses -- I'll add an issue for that.
> Thanks,
> Andy
> -----Original Message-----
> From: Rob van Eijk []
> Sent: Thursday, April 12, 2012 2:00 PM
> To:
> Subject: Re: Issue 2: Use of the term "3rd-party"
> On 9-4-2012 4:33, Andy Zeigler wrote:
> > The reality is that domain names, and not schemes and ports, establish
> > business relationships. By eliminating scheme/port, you get a cleaner
> > list format that's easier to implement.
> I have observed ip-address only tracking sources in the Netherlands. Can
> the list accommodate ip ranges as well? Or is this an edge-case and
> better to be dealt with in eg a /etc/hosts file.
> Rob

Received on Friday, 1 June 2012 17:06:10 UTC