Discuss mailing list

[Theo B <me AT theos.space>]

It does more then just preventing access to .bit domains. If the IP stays blacklisted, anyone who has an ISP that follows Spamhaus's blocklist will not be able to access Fusl's anycast DNS servers. This would suck, because anycast servers are awesome, and we'd lose a T2 :/

On Sat, Dec 17, 2016 at 5:29 PM, <spaesani AT mail.com> wrote:

How exactly does that prevent someone from accessing a .bit domain?
No links, just a brief explanation.

--
Sent from myMail app for Android

Saturday, 17 December 2016, 02:43PM -05:00 from Theo B <me AT theos.space>:

Hi -

So, on thursday a big conversation took place on IRC about Spamhaus deciding to block Fusl's anycast DNS server IPs because a .bit domain was hosting malware. The conversation never really came to a conclusion, so I wanted to throw out some ideas that we talked about.

Here are some of the options we talked about in IRC:

1. Just ignore Spamhaus and move along(This could be bad because some ISPs block the IPs that Spamhaus blocks)

2. Send them an email explaining what we do, and how we're not responsible for any of the content on .bit.. and then hope they remove it.

3. Drop .bit completely, and tell them that the content is no longer there.

What do you people think about this?

-Theo

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org