Re: [opennic-discuss] Vote to keep or drop peering with NameCoin
Jeff Taylor <[email protected]> Wed, 3 Jul 2019 09:41:08 -0600
| Newsgroups | gmane.network.opennic.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1562168477-3952-57 Content-Type: multipart/alternative; boundary="------------ABDFE49A604BC4F5A2796657" Content-Language: en-US This is a multi-part message in MIME format. --------------ABDFE49A604BC4F5A2796657 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Yes. There are quite a number of services that offer adult content filtering as a 'feature'. Net neutrality does not have any bearing on filtering the content, as long as the end-user is made aware of what is being filtered and still agrees to use it. And in the case of opennic, usage is very much optional rather than being mandated as usage terms from a monopolistic internet provider. On 06/30/2019 06:17 PM, Daniel Quintiliani wrote: > Even in countries which mandate net neutrality? > > -- > > -Dan Q > > > On Sun, 30 Jun 2019 17:07:51 -0700, <[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] > > > > > -------- > You are a member of the OpenNIC Discuss list. > You may unsubscribe by emailing [email protected] --------------ABDFE49A604BC4F5A2796657 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Yes. There are quite a number of services that offer adult content filtering as a 'feature'. Net neutrality does not have any bearing on filtering the content, as long as the end-user is made aware of what is being filtered and still agrees to use it. And in the case of opennic, usage is very much optional rather than being mandated as usage terms from a monopolistic internet provider.<br> <br> <br> <div class="moz-cite-prefix">On 06/30/2019 06:17 PM, Daniel Quintiliani wrote:<br> </div> <blockquote type="cite" cite="mid:[email protected]"> <pre wrap="">Even in countries which mandate net neutrality? -- -Dan Q On Sun, 30 Jun 2019 17:07:51 -0700, <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">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" <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">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: </pre> <blockquote type="cite"> <pre wrap="">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: </pre> <blockquote type="cite"> <pre wrap="">Jeff Taylor wrote: </pre> <blockquote type="cite"> <pre wrap="">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. </pre> </blockquote> <pre wrap=""> 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 <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> </pre> </blockquote> <pre wrap=""> -------- You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> </pre> </blockquote> <pre wrap="">-- <a class="moz-txt-link-freetext" href="http://ca.linkedin.com/in/kevinrattai/">http://ca.linkedin.com/in/kevinrattai/</a> <a class="moz-txt-link-freetext" href="https://winnipegcryptoconference.com/">https://winnipegcryptoconference.com/</a> <a class="moz-txt-link-freetext" href="https://github.com/krattai">https://github.com/krattai</a> -------- You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> </pre> </blockquote> <pre wrap=""> </pre> </blockquote> <pre wrap=""> -------- You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> </pre> </blockquote> <pre wrap=""> </pre> <!--'"--><br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap=""> -------- You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> </pre> </blockquote> <br> </body> </html> --------------ABDFE49A604BC4F5A2796657-- ------------=_1562168477-3952-57 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] ------------=_1562168477-3952-57--