Topic: [announce] Namecoin - a distributed naming system based on Bitcoin - page 65. (Read 596107 times)

You obviously changed some proxy settings.
If you got the DNS settings right, don't use any proxies.


I've just checked on Win7 and Mac and Linux. All three domains I recommended (dns.bit, nx.bit, bitse.bit) are up and running.

A few hints:

- Restart your browser after each settings change.
- Try http://nx.bit instead of http://www.nx.bit (some of the active .bit domains haven't configured the "www" subdomain).
- Check both the browser and the system settings: no proxy (e.g. Opera has a proxy system on top of the OS proxy settings).
- Windows7/XP: you may have unchecked/deactivated "TCP/IP" or "IPv4" in the "Properties" window accidentally. Make sure it is active.
- Linux: check /etc/resolv.conf, the first line should be
nameserver 178.32.31.43
(however, some Linuxes don't use this file. Google is your friend   )

Thanks.
Indeed this helped a little bit but only if configured with the proxy 178.32.31.43:8888.
At the beginning it gave me an
It works !
page for every .bit domain but nothing more.
Then I insisted to get more and indeed from  6-7  .bit websites I received the proper page after reloading from "It works !"
From all the others only "Not able to connect.".
Is there any possibility to improve the availability of the .bit websites ?


Yes I saw it and I tried this setup. Thanks. It was very helpful and worked a couple of days but now doesn't work any more.
Now this sites are only working with Khals proxy 178.32.31.43:8888 and resolv.conf changed.
But I am asking how could get working the other .bit websites also.

Already posted this in the other namecoin thread, but I should mention it here, too:



Windows 7:
Control Panel > Network and Internet > Network and Sharing > Connections: Local Area Connection > Properties > IPv4 > Properties > Use the following DNS server > 178.32.31.41

Windows XP:
right-click the mini icon of your active network connection, then select Status > Properties > TCP/IP > Properties > Use the following DNS server > 178.32.31.41

Mac OS:
System Preferences > Network > Advanced > DNS > DNS Servers: +  > 178.32.31.41



(You need an unrestricted user account, of course).


Then open any standard browser and first try one of the following:
http://dns.bit/
http://nx.bit/
http://bitse.bit/

On linux you can put the following line into the top of /etc/resolv.conf

The biggest pain seems to be now browsing .bit domains.

1.
a.
Configuring foxyproxy as described https://dot-bit.org/How_To_Configure_Foxyproxy .
Doesn't work at all with 178.32.31.43:8888.

b.
Changing to 178.32.31.41:80 and trying .bit enabled websites.
Popular .bit enabled websites

bluishcoder.bit
bitcoinX.bit with shortcuts bx.bit and nx.bit (namecoin stats)
bitse.bit (.bit search engine)
dot-bit.bit
explorer.bit
dns.bit
register.bit
14u.bit (URL shortener)
namealert.bit (domain expiration alert)

.bit redirections

bitcoin.bit

Links down or parked

thepiratebay.bit
bitcointorrentz.bit
gee.bit (.bit search engine)
kirk.bit
wikileaks.bit
organicdesign.bit
bitcointalk.bit

Evrywhere is coming the same page:
Namecoin DNS servers
What is namecoin / Dot-BIT ?
How to register a .bit domain

Only register.bit is showing his own content.
It is the same in Ubuntu, Xubuntu, WinXP, Win7, Mozilla and Chromium.
But I remember with the proxy 178.32.31.43:8888 at least the above sites worked half of year ago.

2.
Now I am trying with webproxies:
dotbit.me
You need to register to surf the .bit sites.
 
It is to complicated just to try a site.
proxy.dot-bit.org
Yeah. All the popular .bit sites are working.
But wikileaks not.

3.
Trying dot-bit.addon 1.0 on Mozilla and Chromium from namecoin.com.
Nothing. Could not find server.
With Addblocker and foxyproxy deactivated and restarted also. Nothing again.

4.Trying to configure namecoinia.bit:
{"translate": "namecoinia.org."} browsing not working (with none of the above methods)
{"translate": "namecoinia.org"} browsing not working (with none of the above methods)
with some ns configurations also - browsing doesn't work

------------
Is anybody who has a better experience with it ? or any tricks ?

The compiled windows 3.64 namecoin client is running under wine/xubuntu 10.04.
Next I will try to compile it and run natively. It seems to be not so easy.

I thank namecoin for forcing me to learn the command line, now I can bitcoind getinfo anytime

Some people are not frightened by the command line :p.

People who have registered on my service (http://register.dot-bit.org) and who want to switch to namecoin-qt and manage their names themselves can contact me by pm or mail.


There is currently an important discussion for revised fees on namecoin.
People opinions are welcome on this subject.
This thread will decide how much will cost names and tx in the future :p


I'm also rebasing namecoin on the bitcoin v0.8 code.
I've integrated commits up to bitcoin v0.4.0.
Any help is welcomed on testing this release of namecoind (there is a known bug with name_new causing a crash [any hint on this, backtrace is provided ?] + the wallet encryption does not encrypt in all case [known bug of bitcoin v0.4.0]. So, do not use for production :p).


The Convergence plugin (provide HTTPS support for .bit and self-signed certificates, + namecoin dns resolution in a near future) continue to evolve in parallel with NMControl. A beautiful future for namecoin is coming !

Just to nip any confusion in the bud right here, there never was any 'original namecoin GUI client' ... only ever the namecoind daemon, that you interface with cli rpc calls.

The original Namecoin GUI client is pretty basic. Work is being done on an updated GUI client, though. See this thread: https://bitcointalksearch.org/topic/annnmc-namecoin-wallet-qt-with-integrated-name-registration-v375-236375

Oh, sorry for the ignorance.  Though I don't quite understand what you mean by this...

Fair enough, being able to revoke names after a transfer is probably going too far.  The goal is really only to be able to announce in an unjammable way that one's control over a name has been compromised.  I'm thinking this could be done by allowing a name to be 'double spent' at any point along its history (up to a reasonable limit), where the transaction merely adds a change-of-ownership flag at that point, and therefore doesn't mess with the name's value or who owns it.

Edit: I guess you could just reuse the same address during value updates, and only change addresses when you're transferring ownership.  Address reuse isn't as bad with Namecoin since there's no linking of coins like with Bitcoin, but this would mean public keys are revealed well in advance of a transfer, making them more prone to attack in the event that weaknesses are found in the signing algorithm.  Would these special flagging transactions be worth adding in order to keep public keys secret?

you can do that now...    the idea is to make the value data cost and then let the user decide

If somebody steals your private keys you are out of luck (just as with Bitcoin). It might be possible to have layers of two or more names where you can keep the first level more secure than the second level and can use the first level to revoke the second level. E.g. the master name imports a secondary name that is used for everyday business. All this is not implemented as of now.

I've been spending a bit of time learning about Namecoin, and a couple questions/thoughts came to mind: 

1) Would it make more sense for the Namecoin blockchain to only know about (name, hash(value)) pairs instead of the full values?  Storage and serving of full values could then remain optional for blockchain-verifying nodes, and there would be a great deal of flexibility with how (hash(value), value) pairs are stored and served - e.g. a DHT could be used to store and serve these, but there doesn't have to be one single way.  Then nodes could be discerning about what data they want to store and serve, while still being able to verify the Namecoin blockchain.  It would also reduce the necessary burden on miners, making them more likely to mine.

2) Proper name revocation seems to be a necessary feature for Namecoin to function as a PKI, so I'm wondering if this is addressed?  If yes, then if the private key controlling my name is compromised and an attacker transfers control of the name to himself, do I have any time window to revoke the name altogether?  If I revoke a name, how long before somebody can claim it?  If name revocation isn't currently possible, do the devs think it would be a valuable enough feature to support?

Great intro article on Coindesk.

http://www.coindesk.com/what-are-namecoins-and-bit-domains/

or up vote at reddit if you want to get others to have a read

http://www.reddit.com/r/Bitcoin/comments/1gltoi/what_are_namecoins_and_dot_bit_domains/

 

added name filter to Manage Names..

I will update this thread for QT Updates (apart from major updates) in the future
https://bitcointalksearch.org/topic/annnmc-namecoin-wallet-qt-with-integrated-name-registration-v375-236375

We will update the news thread with latest official releases along with other software

Nice, eager to see NMC actually get used, (not only sold/brought)

Namecoin News Thread: https://bitcointalksearch.org/topic/nmc-namecoin-news-thread-236340

Great job

If the wallet is not encrypted, "encryptwallet" appears. Otherwise "walletpassphrase" appears. This is normal, and it is the way it's done in Bitcoin.

strange..

what OS are you on?

i get the following extra commands (on windows)
walletlock
walletpassphrase
walletpassphrasechange

will get it looked at asap