Nice to hear that I am not the only one who was not able.phelix wrote:I am still testing. So far it looks very good
I could not yet get it running in the Tor browser bundle... do you have any idea why that could be? I deactivated the https everywhere extension to no avail.
It works fine with normal Firefox: http://duskgytldkxiuqc6.onion --> http://federalistpapers.bit
Let me tell you my experience.
I tried on 32 bit xubuntu 10 and 12 VM native and with wine without reading the installation description but didn't worked.
Then I read the descriptions so I tried next on a 64bit W8 system directly. By the bundle option the Mozilla plugin downloaded the blockchain and after it .bit domains mostly worked(if not then worked again after restart).
But doesn't resolve to TOR. Of course not because TOR is not started. However not immediately you realize that Tor and I2P is not working because always there is a standard message on klicking .bit domains which should resolve to Tor or I2P.
Welcome to nginx!
which doesn't correspond to the content on http://duskgytldkxiuqc6.onion.
OK. I need Tor or I2P to work also from the browser.
Next I tried from the TBB but there doesn't work at all the .bit resolving, not even after deactivating the HTTPS and the NOSCRIPT plugins.
So namecoind seems to work when Mozilla started then I tried to connect TBB to namecoind - not succeeded.
TBB(with the plugin) doesn't work also if the option 'bundle' activated.
Now I see 3 possible directions to get forward working the plugin with Tor:
1. to get TBB somehow to work with the plugin (a bundled version TBB with the .bit plugin would be ideal)
2. Mozilla which is working with the plugin without Tor to configure somehow with an alone standing Tor. I still remember the times when this was necessary to get working Tor because TBB didn't existed. This old informations needs to be grabbed out and maybe adapted.
3. To put the working Mozilla with .bit plugin in a Whonix workstation which is connected to the Tor gateway.
However the standard workstation is a 32 bit Debian and a 64 bit system is needed for the plugin.
A 64 bit VM(or isolated machine) needs to be created which is still not tested how it works with the gateway.(but theoretically should work)