Hacker News new | ask | show | jobs
by GrryDucape 2457 days ago
Is it just me or has this DNSCrypt project been doing things without any prior announcement?

Last month or so, the main GitHub repo for DNSCrypt randomly got deleted. It wasn't until several days later, the author posted a tweet saying he/she are not supporting it anymore.

Now it has seemingly been resurrected...after I have already configured my server to use a new project called getdns (and stubby).

3 comments

Hi!

The GitHub repository for dnscrypt-proxy was simply moved from my personal GitHub account to the DNSCrypt organization. GitHub automatically adds redirections when a project is moved, so this should be transparent.

dnscrypt-proxy 2 is actively supported since it was released in January 2018. What has been EOL'd is the legacy dnscrypt-proxy 1.x client, after having been supported for 7 years.

The protocol itself is also still evolving, with the recent introduction of a lightweight alternative to Tor in order to hide IP addresses: https://raw.githubusercontent.com/DNSCrypt/dnscrypt-protocol...

Besides the main website https://dnscrypt.info, there is a subreddit for announcements: https://www.reddit.com/r/dnscrypt/

What happened to DNSCrypt-OSXClient Preferences? It was suddenly pulled from Homebrew.
Yes, I'm aware of that, but I don't use Bitbar, and I'm wondering about what happened with that Homebrew Cask. Why was it pulled, and why was the orig. pulled?

I normally use WireGuard and use a DNS server supplied by that. If WireGuard is offline, I automatically use DNSCrypt.

The project have a turbulent history IMO.

Been using it for years, but did not know of the recent episode. Leaves you wondering..

Stubby is kind of limited. It has no cache, and I can't find a way to avoid resolving a list of my own domains via a specified resolver, so it's not that great for privacy.
Though I like getdns C API, I'll probably use it in one of my projects.