Yes. We're collaborating with GNUnet to get .bit (and .gnu) registered as special purpose TLD's. Same for I2P. There appears to be some political resistance at IETF to Namecoin and GNUnet, which wasn't the case for Tor (or I2P). See https://gnunet.org/ietf93dnsop . We're still hoping for a positive outcome.
I like it! It loads quickly for me and looks great.
Google isn't absolutely in love with it's architecture though as seen here: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fnamecoin.org%2F
Might want to consider configuring the viewport and moving any javascript files to the bottom of the page. It will take a few seconds and greatly improve the potential loading speed (and thus the potential ranking) in Google's googley eyes.
Cacheing is pretty simple to implement as well, which isn't being done apparently.
Looking pretty good on this checker, though!
Cheers to you!
Having a commit of a names data structure in the block header would allow extremely lite clients, that could resolve .bit domain names and be embedded in browsers.
Lighthouse is entering public beta this month:
https://groups.google.com/forum/#!msg/lighthouse-discuss/jNkHuoaWeDY/tlswlp_cXu0J
We could use it to do a fundraiser for the development of this addition.
I agree with your proposals but $ is the difference, many of this coins had bounties paid with "premine" or were IPO coins like NXT etc.
NMC has a bounty program but very few people donate to the NMDF Namecoin Marketing and Development Fund.
NMC developers are mostly volunteers. I moderate here all day because i'm unemployed, etc.
Thanks for the speedy reply Jeremy. I feared this was the case because even if the user has .bit enabled DNS the fingerprint lookup can't be done over DNS as it stands now. Requiring a plugin to authenticate the cert seems like too much of a hack to be of any use for the real world.
I wonder if Let's Encrypt will support .bit, it may not be decentralised but it would work for now.
Totally agree re: Namecoin decentralised certificate authentication being a huge plus, not even just decentralised but incredibly secure too (providing the private key is safe).
Namecoin fans are probably more likely to be fans of Ricochet: https://ricochet.im/ . Ricochet is decentralized (other than the centralized parts of Tor itself), while Tor Messenger has centralized servers that can collect metadata. "We kill people based on metadata." Not to say that Tor Messenger is useless; if for some reason you absolutely need to communicate with someone on a centralized service, Tor Messenger can be useful. But the design that Ricochet uses is definitely safer, assuming that you can get your friends to use it.
Side note: if someone is interested in adding Namecoin identity support to Ricochet, that would be a worthwhile project -- ping me on IRC.
doublec mentioned once he was working on something firefoxy, although I believe it was more of a custom build than an addon.
I have some code that can act as a local namecoin resolver, although it also needs namecoin running on the box too. If you can install and run both, then point firefox's socks proxy settings at the resolver, you have a self-sufficient browsing setup with no middle man. An addon could probably make the whole process easier.
i couldn't get the latest version to work either. i had exactly the same problem. so I used an older version 32191, git commit bdf77399db427ba4eedcec2b3057c4ba029d8113
click download and this version should get you to compile and work
I am curious why they even bothered to mention blockstack so early on back then? A project that is still yet to launch all of these months later and curiously claims that they have "13,363 community devs" on blockstack.org whatever that means?
What are namecoiner's opinions of Blockstack technology?
To be honest, I have never even heard of them until just now... and they're hosting and ethereum based token ICO as we speak... surprise surprise!
>Anything that does not innovate, does not survive.
That's quite a broad stroke, don't you think?
Ideas are great, but don't write off Namecoin because it does one thing really well.
The graphite pencil hasn't innovated in over 250 years and it's still going strong.
(Yes, I just linked a blog that focuses exclusively on pencils)
>Think about it. How many people want to keep on renewing a domain name every 6 months as opposed to every 12 months.
Apparently over 5 million people have no problem renewing their SSL certificate every 90 days.
Aim of this bundle is to provide an all in one package that people can install to really use the decentralized part of the namecoin DNS system, instead on relying on external DNS or proxy servers for .bit domains.
How to use it :
Unzip on the desktop (or where you want)
linux : Launch (on gnome, select : Launch in a terminal, must stay open, otherwise relaunch)
windows : Launch , then (both must stay open, otherwise relaunch)
Configure FoxyProx : Go to "Tools" → "Foxy Proxy Standard" → "Options", Open "File" → "Import Settings" and select the file "" (works for IE and chrome too)
The alerts list is at https://groups.google.com/forum/#!forum/namecoin-alerts ; the information about BIP66 enforcement being imminent was posted there yesterday. For some reason BitMinter had been checking an old alert list that was hosted by Khalahan, whose server had been decommissioned last year. We've informed BitMinter about the current alerts list.
I'm actually not familiar with the term "compressed addresses". Is this related to compressed public keys? If so, my understanding from https://bitcoin.org/en/developer-guide#public-key-formats is that since this was handled by OpenSSL in older versions of Namecoin, and OpenSSL handles compressed public keys without any issues, it's probably going to be fine. In fact, I assume that current Namecoin Core releases generate compressed public keys. All that said, I haven't tested this, so try it at your own risk.
Yes, that is the trick I was thinking of. You'll still run into issues if for some reason you want some domains to use HTTP and others HTTPS. While I generally dislike such policies (HTTPS should be used for everything), there are tricks for making that work too. I think this is relevant, but I haven't tried it: https://stackoverflow.com/questions/1175096/how-to-find-out-if-youre-using-https-without-serverhttps
i'm not sure about reliable wallets from android since coinomi leaved us stranded, the app i would recomend right now is the one from coinex. this seems to be one of the last exchanges, but volume is suspiciously fake.
I would recomend to withdraw to your wallet (trezor hardware wallet) , asap, in case this exchange gets hacked like livecoin and altilly.
DO NOT TRY YOBIT exchange, is a scam and can't withdraw NMC from there!
No, but I bought some on wex.nz for a pretty high price. I'm now selling small amounts (around 1 nmc) for a reasonable price on bisq (https://bisq.network/), for those who want to experiment with namecoins and register bit domains, etc..
Quick and dirty instructions to test:
xcode-select --install
When the popup appears, click Install
.
Then install Homebrew.
brew install automake berkeley-db4 libtool boost --c++11 miniupnpc openssl pkg-config protobuf qt libevent
brew install librsvg
git clone https://github.com/namecoin/namecoin-core
cd namecoin-core
git pull origin pull/179/head
./autogen.sh
./configure
make
make check
make deploy
The make deploy
step is what we're hoping works properly. Specifically, we're hoping that it creates Namecoin-Qt.dmg
(not Bitcoin-Qt.dmg
), that the app inside the .dmg
file is called Namecoin-Qt.app
(not Bitcoin-Qt.app
), that the rest of the stuff inside the .dmg
and .app
files uses the name "Namecoin" instead of "Bitcoin", and that the .dmg
file can be installed without any weird bugs. (I expect that the Bitcoin logo will still be there in a few places, that's an orthogonal bug.)
EDIT: Fixed formatting oddities, seems that Reddit's Markdown isn't the same as GitHub's.
> make sure that the DNS you are using supports *.bit addresses. I think you can find some here https://www.opennic.org/ > > I just tested 51.15.98.97 DNS, this one resolves *.bit names.
Don't recommend centralized inproxies in this subreddit.
{ "ip": "X", "map": { "*": { "ip": "X" } } }
Is the correct format. After the name is updated in the namechain make sure that the DNS you are using supports *.bit addresses. I think you can find some here https://www.opennic.org/
Sounds like CurveCP.
i2p does this already, although it is (deliberately, to avoid anonymity leaks) not inter-routable with the clearnet IP network at any level, whereas CurveCP is (at the transport layer) and (it seems) Snow is too.
The trick (popularized by bitcoin but probably predating it) of using hashes of public keys as addresses, instead of the longer keys themselves, would be very useful here. I suppose one could argue that the hashofpubkey-to-pubkey lookup process is its own separate protocol, like DNS, but with infinite TTLs and zero trust required.
It would also be a good idea to use a denser coding than Base36, although that's an API innovation that can be slapped on after the fact.
Well, "Keybase is now writing to the blockchain"
With a little bit of imagination, everything is just some form of a nail :)
There is already another method that is probably more robust and useful for extension to other proxy settings also, FoxyProxy add-on. At the official namecoin wiki page:
> things like Roald Dahl's James and the Giant Peach
LOL, that's one of the few books that I actually did enjoy reading in school. Haven't heard of or even thought of that book for quite some time now.
>when books 4 through 7 came out, I read each of them in about 1.5 days
I have not had the pleasure of reading any harry potter books yet unfortunately.
I was "too old" (in my mind) for them when they first came out, and I just ignored them all because I thought it was a childish venture.
So I guess "mimbleWimble" and the grin project mean a lot more to you than they would to me?! I think I've only even seen one of the films even...
Speaking of reading... I have re-acquainted myself with it recently and I am absolutely loving the book by Robert Pirsig called "Zen and the Art of Motorcycle Maintenance, An Inquiry Into Values".
Ever heard of it? I only began reading it because I have seen that book referenced on HN more than any other book probably... and I can see why now.
I am beginning to worry that I have a little bit of Phaedrus in me :S
>I wasn't reading the newspaper when I was 4, but I definitely picked up reading a lot quicker than most kids.
You've got a special brain man, take care of it!