Re: [opennic-discuss] Vote to keep or drop peering with NameCoin
Amunak <[email protected]> Sun, 30 Jun 2019 12:05:37 +0200
| Newsgroups | gmane.network.opennic.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1561889143-3952-48 Content-Type: multipart/alternative; boundary="------------FB713EBECA37C57FEB2EEA7E" Content-Language: en-US This is a multi-part message in MIME format. --------------FB713EBECA37C57FEB2EEA7E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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] --------------FB713EBECA37C57FEB2EEA7E 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"> <p>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.</p> <p>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.</p> <p>Amunak</p> <div class="moz-cite-prefix">On 30.06.2019 1:55, Jacob Bachmeyer wrote:<br> </div> <blockquote type="cite" cite="mid:[email protected]">Jeff Taylor wrote: <br> <blockquote type="cite">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. <br> </blockquote> <br> 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. <br> <br> 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? <br> <br> <br> -- Jacob <br> <br> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <pre class="moz-quote-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> </body> </html> --------------FB713EBECA37C57FEB2EEA7E-- ------------=_1561889143-3952-48 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] ------------=_1561889143-3952-48--