Re: [opennic-discuss] Vote to keep or drop peering with NameCoin
Rouben <[email protected]> Sun, 30 Jun 2019 20:17:49 -0400
| Newsgroups | gmane.network.opennic.general |
|---|---|
| Message-ID | <CAGShw4ni-zPcqzjAJ6Nbj4g+LPw37GLwNEiHo6NuEaf_y6VF2A@mail.gmail.com> |
This is a multi-part message in MIME format... ------------=_1561940284-3952-54 Content-Type: multipart/alternative; boundary="000000000000907d64058c938fc6" --000000000000907d64058c938fc6 Content-Type: text/plain; charset="UTF-8" Even universities do it... for example filter domains of phishers. I happen to work for one and can vouch for this. On Sun, Jun 30, 2019 at 20:08 <[email protected]> wrote: > I think you're wrong about that. A quick google and > you'll see that DNS filtering is actually quite common. > > ~ Ole > > > On Sun, 30 Jun 2019 18:56:32 -0400 (EDT) > "Daniel Quintiliani" <[email protected]> wrote: > > > No ISP in the free world does this with their DNS > > servers. Why should we? > > > > -- > > > > -Dan Q > > > > > > On Sun, 30 Jun 2019 15:58:11 -0500, kevin > > <[email protected]> wrote: > > > > > The problem here was, spamhaus painted ALL opennic > > > peers with a broad brush. So those that won't filter > > > anything, which I fully support, could potentially > > > affect everyone. > > > > > > As many, if not most of us here appear to believe, this > > > project has always been about freedom with > > > collaboration via a touch of democracy (voting) thrown > > > in. And I believe that everyone can (and will) do as > > > they please. > > > > > > But... and so to repeat, those that filter nothing > > > (including malware) could affect all of us. And like > > > the .free domain, I don't care and would have preferred > > > to keep it under openNIC. But, not everyone agrees > > > with what I think. lol So filtering, at least for > > > malware, certainly could be suggested as a strong > > > guideline or recommendation. And my opinion with > > > anything else, obviously leave that to the individual > > > T2 hosts. > > > > > > Kevin > > > > > > On Sun, 2019-06-30 at 12:05 +0200, Amunak wrote: > > > > Why? The T2 server list is capable of displaying and > > > > filtering pretty > > > > much anything. Some T2 server providers may choose to > > > > run more blacklists, some may choose to run none. > > > > That's their decision and as > > > > long as they say so in their server's description > > > > then more power to everyone - the whole point of > > > > sharing T2 servers is to provide a service > > > > to other users who have an interest in that service > > > > *with that particular configuration*. Same goes for > > > > logging and such. > > > > > > > > Sure, don't show it on the homepage among > > > > "recommended servers" but there's no reason to > > > > essentially blacklist those servers and operators > > > > from OpenNic. > > > > > > > > Amunak > > > > > > > > On 30.06.2019 1:55, Jacob Bachmeyer wrote: > > > > > Jeff Taylor wrote: > > > > > > It could relate to any domains, opennic or > > > > > > icann. And I'm not saying > > > > > > we WILL, I'm just saying we COULD have that > > > > > > option. Like with the > > > > > > spamhaus listings, use of this would be up to the > > > > > > individual T2 operators. At the moment there is > > > > > > nothing planned, I just wrote the > > > > > > API so we could expand on its use later if we > > > > > > chose to. > > > > > > > > > > I suggest a policy restricting the use of > > > > > non-malware blacklists to > > > > > private T2 servers. In other words, T2 servers > > > > > using blacklists for > > > > > any category other than malware would not be > > > > > eligible to be listed in > > > > > the public directory. > > > > > > > > > > We might even want to require public T2 servers to > > > > > blacklist known malware domains, but that is sure > > > > > to be highly controversial. Should > > > > > we censor ransomware? > > > > > > > > > > > > > > > -- Jacob > > > > > > > > > > > > > > > > > > > > -------- > > > > > You are a member of the OpenNIC Discuss list. > > > > > You may unsubscribe by emailing > > > > > [email protected] > > > > > > > > -------- > > > > You are a member of the OpenNIC Discuss list. > > > > You may unsubscribe by emailing > > > > [email protected] > > > -- > > > http://ca.linkedin.com/in/kevinrattai/ > > > > > > https://winnipegcryptoconference.com/ > > > > > > https://github.com/krattai > > > > > > > > > -------- > > > You are a member of the OpenNIC Discuss list. > > > You may unsubscribe by emailing > > > [email protected] > > > > > > > > -------- > You are a member of the OpenNIC Discuss list. > You may unsubscribe by emailing > [email protected] > -- Rouben --000000000000907d64058c938fc6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div><div dir=3D"auto">Even universities do it... for example filter domain= s of phishers. I happen to work for one and can vouch for this.</div></div>= <div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O= n Sun, Jun 30, 2019 at 20:08 <<a href=3D"mailto:[email protected]">[email protected]</a>= > wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 = 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think you're wron= g about that. A quick google and<br> you'll see that DNS filtering is actually quite common.<br> <br> ~ Ole<br> <br> <br> On Sun, 30 Jun 2019 18:56:32 -0400 (EDT)<br> "Daniel Quintiliani" <<a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a>> wrote:<br> <br> > No ISP in the free world does this with their DNS<br> > servers. Why should we?<br> > <br> > --<br> > <br> > -Dan Q<br> > <br> > <br> > On Sun, 30 Jun 2019 15:58:11 -0500, kevin<br> > <<a href=3D"mailto:[email protected]" target=3D"_blank">krattai@gma= il.com</a>> wrote:<br> > <br> > > The problem here was, spamhaus painted ALL opennic<br> > > peers with a broad brush.=C2=A0 So those that won't filter<br> > > anything, which I fully support, could potentially<br> > > affect everyone.<br> > > <br> > > As many, if not most of us here appear to believe, this<br> > > project has always been about freedom with<br> > > collaboration via a touch of democracy (voting) thrown<br> > > in. And I believe that everyone can (and will) do as<br> > > they please.<br> > > <br> > > But...=C2=A0 and so to repeat, those that filter nothing<br> > > (including malware) could affect all of us.=C2=A0 And like<br> > > the .free domain, I don't care and would have preferred<br> > > to keep it under openNIC.=C2=A0 But, not everyone agrees<br> > > with what I think. lol=C2=A0 So filtering, at least for<br> > > malware, certainly could be suggested as a strong<br> > > guideline or recommendation. And my opinion with<br> > > anything else, obviously leave that to the individual<br> > > T2 hosts.<br> > > <br> > > Kevin<br> > > <br> > > On Sun, 2019-06-30 at 12:05 +0200, Amunak wrote:=C2=A0 <br> > > > Why? The T2 server list is capable of displaying and<br> > > > filtering pretty <br> > > > much anything. Some T2 server providers may choose to<br> > > > run more blacklists, some may choose to run none.<br> > > > That's their decision and as <br> > > > long as they say so in their server's description<br> > > > then more power to everyone - the whole point of<br> > > > sharing T2 servers is to provide a service <br> > > > to other users who have an interest in that service<br> > > > *with that particular configuration*. Same goes for<br> > > > logging and such.<br> > > > <br> > > > Sure, don't show it on the homepage among<br> > > > "recommended servers" but there's no reason to= <br> > > > essentially blacklist those servers and operators <br> > > > from OpenNic.<br> > > > <br> > > > Amunak<br> > > > <br> > > > On 30.06.2019 1:55, Jacob Bachmeyer wrote:=C2=A0 <br> > > > > Jeff Taylor wrote:=C2=A0 <br> > > > > > It could relate to any domains, opennic or<br> > > > > > icann.=C2=A0 And I'm not saying <br> > > > > > we WILL, I'm just saying we COULD have that<br> > > > > > option.=C2=A0 Like with the <br> > > > > > spamhaus listings, use of this would be up to the<= br> > > > > > individual T2 operators.=C2=A0 At the moment there= is<br> > > > > > nothing planned, I just wrote the <br> > > > > > API so we could expand on its use later if we<br> > > > > > chose to.=C2=A0 <br> > > > > <br> > > > > I suggest a policy restricting the use of<br> > > > > non-malware blacklists to <br> > > > > private T2 servers.=C2=A0 In other words, T2 servers<br> > > > > using blacklists for <br> > > > > any category other than malware would not be<br> > > > > eligible to be listed in <br> > > > > the public directory.<br> > > > > <br> > > > > We might even want to require public T2 servers to<br> > > > > blacklist known malware domains, but that is sure<br> > > > > to be highly controversial. Should <br> > > > > we censor ransomware?<br> > > > > <br> > > > > <br> > > > > -- Jacob<br> > > > > <br> > > > > <br> > > > > <br> > > > > --------<br> > > > > You are a member of the OpenNIC Discuss list.<br> > > > > You may unsubscribe by emailing <br> > > > > <a href=3D"mailto:[email protected]= ect.org" target=3D"_blank">[email protected]</a>= =C2=A0 <br> > > > <br> > > > --------<br> > > > You are a member of the OpenNIC Discuss list. <br> > > > You may unsubscribe by emailing <br> > > > <a href=3D"mailto:[email protected]= rg" target=3D"_blank">[email protected]</a>=C2= =A0 <br> > > -- <br> > > <a href=3D"http://ca.linkedin.com/in/kevinrattai/" rel=3D"norefer= rer" target=3D"_blank">http://ca.linkedin.com/in/kevinrattai/</a><br> > > <br> > > <a href=3D"https://winnipegcryptoconference.com/" rel=3D"noreferr= er" target=3D"_blank">https://winnipegcryptoconference.com/</a><br> > > <br> > > <a href=3D"https://github.com/krattai" rel=3D"noreferrer" target= =3D"_blank">https://github.com/krattai</a><br> > > <br> > > <br> > > --------<br> > > You are a member of the OpenNIC Discuss list. <br> > > You may unsubscribe by emailing<br> > > <a href=3D"mailto:[email protected]" t= arget=3D"_blank">[email protected]</a>=C2=A0 <br> > <br> > <br> <br> <br> <br> --------<br> You are a member of the OpenNIC Discuss list. <br> You may unsubscribe by emailing <a href=3D"mailto:discuss-unsubscribe@lists= .opennicproject.org" target=3D"_blank">[email protected]= ject.org</a><br> </blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" = data-smartmail=3D"gmail_signature">Rouben</div> --000000000000907d64058c938fc6-- ------------=_1561940284-3952-54 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit -------- You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing [email protected] ------------=_1561940284-3952-54--