Matthew Zipkin

**Handshake is, by design, on a collision course with ICANN.** When it happens is not really relevant. This project is about fighting for freedom, not compliance with legacy authority (ENS...

@dnsguru with the exception of `music`, could you provide a complete list of the names in question and if possible the range of dates you anticipate their resolution in the...

As the mathematicians like to say "the solution exists". https://github.com/handshake-org/hsd/pull/558 is merged, and the https://github.com/pinheadmz/holdmyhand plugin has been released. Users or services interested in applying extra protection can do so...

@dnsguru we aren't changing any "general protocol" rules any time soon, maybe ever. I recommend you focus your energy on convincing users and services to run hsd with the holdmyhand...

> More of an fyi than a problem, the prefix path not existing is fatal (whereas hsd creates the directory). What do you think about creating the folder if it...

This baby just went through a rigorous rebase. @nodech and @buffrr I explored using libuv for async file i/o and it was too problematic, especially during IBD if we write...

added check for `cd` bit: ``` --> dig @127.0.0.1 -p 5350 dnssec-failed.org ; DiG 9.16.10 @127.0.0.1 -p 5350 dnssec-failed.org ; (1 server found) ;; global options: +cmd ;; Got answer:...

hm... so hnsd's recursive resolver (from libunbound) is forwarding `com` to your other unbound resolver, but when your recursive goes to check the DNSSEC, it asks hnsd for `"."` which...

What are you trying to accomplish by forwarding the `com` zone? It's already passed pi-hole at this point, why not just let hnsd be the ultimate recursive? Just trying to...

Ok cool so this is the same issue as #53 and I tried fixing with #62 but its a doozy, I'll have to come back to this. The goal of...