This is mostly about resolving .bit
inside Whonix? Or and/or namecoin wallet?
To resolve .bit
is installation of namecoind required? Would namecoind (or anything) need to download a ~ 300 GB blockchain? What are the disk space requirements? Or can ncdns
be used standalone?
A separate VM for namecoin only seems overkill indeed at this point.
Realistic to get namecoin integrated into Tor instead the browser (Tor Browser)?
How to start simpler…? Using namecoin on Debian? The web search results for that aren’t great.
I am asking because perhaps namecoin integration would be easier if done on Whonix-Gateway.
Would also be interesting to see how Tails integration would go. (Tails used to have monkeysphere and i2p integration. Wondering if that indicates openness for namecoin integration.)
Ideally this could be implemented as an add-on package. That would be cleaner. This is even unspecific to Whonix. Also for users of Debian it would be much better if they could “sudo apt install namecoin”.
(The request for being an add-on package is unrelated to Namecoin Integration in Whonix, opt-in vs default installation.)
Using ncdns
requires modification of system DNS configuration file /etc/resolv.conf
as far as I understand. For sake of being an add-on package, for better usability, could you please support something like /etc/resolv.conf.d
? I think that requires package resolvconf
. Long ago since I looked into that. Avoided for lower complexity. Maybe now would be a time to reconsider that.
By supporting dropping a snippet into /etc/resolv.conf.d
things would look much better. In my very strong opinion, Debian (and similar for other Linux distribution) installation experience needs to boil down to a “sudo apt install namecoin” level of simplicity. An “oh but you need to edit /etc/resolv.conf
” would be a major usability issue.
Needing to edit a configuration file such as /etc/resolv.conf
is bad. Not exactly but Modifying Default Configuration of Third Party Packages is realted. I can make a stronger case for that if needed.
ncdns
supports using Tor’s SocksPort
? (If ncdns
isn’t needed / supposed for this use case then might question might not make sense / not be important.)