--===============1557523090==
Content-Type: multipart/signed;
  boundary="nextPart2808265.mEZyFWUfeZ";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2808265.mEZyFWUfeZ
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

David Faure wrote:
>Oh. Shouldn't we have two blacklists then?
>When I suggested the name "ipv6blacklist" on IRC, it was for "don't do
> ipv6 but to ipv4 on those servers", which would be the way to access a
> banking site with a buggy DNS server of its own, right?
>
>And then you could have a "blacklist" directory with the "completely
> blacklisted, e.g. ad sites" list.

That's a workaround. My opinion is that we should completely blacklist=20
buggy sites so that it hits them where it hurts the most: their pockets.=20
That is specially true for adserver sites.

I hadn't considered the situation when people wanted to access the buggy=20
sites themselves.

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

5. Swa he g=C3=A9anhwearf t=C3=B3 timbran, and hwonne he c=C3=B3m, l=C3=A1!=
 Unix cw=C3=A6=C3=B0 "Hello,=20
World". =C7=BCfre =C7=BDghwilc w=C3=A6s gl=C3=A6d and seo woruld w=C3=A6s f=
r=C3=A9o.

--nextPart2808265.mEZyFWUfeZ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBB9q4vM/XwBW70U1gRAh7BAKCPBsngjEgMrgV06jeEck5gto3YRQCgwvJ2
EkdxluXyXM7FgjJJcv5s+X0=
=v6UQ
-----END PGP SIGNATURE-----

--nextPart2808265.mEZyFWUfeZ--

--===============1557523090==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1557523090==--