rykigam
Newbie
Offline
Activity: 57
Merit: 0
|
|
July 22, 2011, 01:36:49 PM |
|
is there a gui inside namecoin.exe ? after starting i get a black window and see that the data files will rise kb's ...
but over 10 min no gui ...
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
July 22, 2011, 01:50:35 PM |
|
is there a gui inside namecoin.exe ?
There is no gui. it's all controlled by the JSON-RPC server, similar to bitcoind.
|
|
|
|
burp
Member
Offline
Activity: 98
Merit: 10
|
|
July 22, 2011, 07:48:49 PM |
|
What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
|
|
|
|
Shinobi
|
|
July 22, 2011, 07:55:49 PM |
|
When? More like an "if", and a remote one at that! What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
|
_______ Thinking of using a cheap, yet reliable VPN? Go with PrivateInternetAccess. Not a referral link. Just a satisfied customer!
|
|
|
ctoon6
|
|
July 22, 2011, 08:20:26 PM |
|
the .bit domain could easily be changed because domains are registered as d/name here
so if i wanted ctoon6.bit
i register as d/ctoon6
so you could probably change a few lines of code and use a completely different domain name.
|
|
|
|
imperi
|
|
July 22, 2011, 10:44:35 PM |
|
When? More like an "if", and a remote one at that! What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
Holy crap! Shinobi made his first non-bear post! Stop the presses!
|
|
|
|
ANSYSiC
Newbie
Offline
Activity: 27
Merit: 0
|
|
July 25, 2011, 04:31:29 PM |
|
|
|
|
|
talpan
|
|
July 30, 2011, 07:31:13 PM |
|
If someone is interested in a Bitcoin/Namecoin trading, join PoolMunity. We have a very low fee of 0.1% .
|
|
|
|
phelix
Legendary
Offline
Activity: 1708
Merit: 1020
|
|
August 13, 2011, 02:22:27 PM |
|
it's really easy to add namecoin support to firefox using foxyproxy - sweet.
how much trouble is it for a webhoster to add .bit support if you do not have your own ip? and what would he have to do?
|
|
|
|
|
khal
|
|
October 25, 2011, 10:40:27 PM Last edit: November 14, 2011, 04:56:39 PM by khal |
|
Last news from namecoin / dot-bit :- Merged Mining is active since october 8 and is working like a charm. Network power has moved from 500GHash/s to 2000/3000GH/s, and it's not finished yet ! Bitcoin / Namecoin ratio is now below 10. - Version 0.3.24.64 has been released, please update, it's a security release. - 3000 valid domains names reached today ! (for a total of 3030 names). - a php script ( NamecoinToBind) is available if you want do make your own bind server with .bit support
|
|
|
|
Red Emerald
|
|
October 26, 2011, 12:06:32 AM |
|
Just got my miner setup with merged mining on Eligius with 1GH/s.
I already run my own DNS server for my own personal websites. I'll play around with the PHP->bind scripts over the next few days and let you know what I think.
|
|
|
|
khal
|
|
November 14, 2011, 04:56:16 PM |
|
I already run my own DNS server for my own personal websites. I'll play around with the PHP->bind scripts over the next few days and let you know what I think.
Any news about your DNS server ?
|
|
|
|
Gabi
Legendary
Offline
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
|
|
November 14, 2011, 06:03:54 PM |
|
What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one.
|
|
|
|
Red Emerald
|
|
November 14, 2011, 06:44:39 PM |
|
I already run my own DNS server for my own personal websites. I'll play around with the PHP->bind scripts over the next few days and let you know what I think.
Any news about your DNS server ? I ended up just setting up a forward. My nameserver doesn't have PHP installed on it, as I'm playing with some other projects in python. zone "bit" { type forward; forwarders { 178.32.31.41; // French bit DNS 78.47.86.43; // German bit DNS }; };
It's an internal DNS, otherwise I'd publish the IP.
|
|
|
|
bulanula
|
|
November 14, 2011, 06:50:25 PM |
|
You guys need to hurry up :
-rescan functionality still not working -wallet encryption not working -GUI nowhere to be found -alternate clients without TX fees requirement ?
|
|
|
|
marcus_of_augustus
Legendary
Offline
Activity: 3920
Merit: 2349
Eadem mutata resurgo
|
|
November 17, 2011, 10:08:28 PM |
|
You guys need to hurry up :
-rescan functionality still not working -wallet encryption not working -GUI nowhere to be found -alternate clients without TX fees requirement ?
They will be open for help I'm sure. If you were a paying customer it may be different .... but you are not.
|
|
|
|
julz
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
November 17, 2011, 10:29:47 PM |
|
What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one. That situation seems decidedly un-nothing-like to me, and awfully browser-centric. As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain. Scripts/email systems etc can then resolve .bit names without specific configuration. The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place.
|
@electricwings BM-GtyD5exuDJ2kvEbr41XchkC8x9hPxdFd
|
|
|
marcus_of_augustus
Legendary
Offline
Activity: 3920
Merit: 2349
Eadem mutata resurgo
|
|
November 17, 2011, 11:01:34 PM |
|
What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one. That situation seems decidedly un-nothing-like to me, and awfully browser-centric. As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain. Scripts/email systems etc can then resolve .bit names without specific configuration. The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place. Why would ICANN want to use .bit TLD in the first place ... see how much resistance they put up to extending beyond the limited set they began with. Adding in .bit for them would create more confusion than clarity. There is little upside for them to commandeer it at this stage. Why would they it is not like it is .com or .org ...
|
|
|
|
julz
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
November 17, 2011, 11:09:37 PM |
|
What happens when the .bit domain gets officially used by ICANN? Has anyone thought about that?
Nothing? Since namecoin is a different dns system, the two can work together. Of course you need to tell your browser if the .bit address you are looking for is a namecoin one or a normal icann one. That situation seems decidedly un-nothing-like to me, and awfully browser-centric. As it currently stands, DNS resolver operators can add transparent support for the .bit space 'as if' it were the same as any other toplevel domain. Scripts/email systems etc can then resolve .bit names without specific configuration. The fact that ICANN may effectively yank this mode of operation out from under us (you can bet nearly all resolver operators will revert to resolving official ICANN names) is surely a risk which may make it hard to convince operators to support it in the first place. Why would ICANN want to use .bit TLD in the first place ... see how much resistance they put up to extending beyond the limited set they began with. Adding in .bit for them would create more confusion than clarity. There is little upside for them to commandeer it at this stage. Why would they it is not like it is .com or .org ... Because they're pretty much opening up arbitrary toplevel domains to whoever has deep enough pockets and the facilities to run a name registry. The risk is that *someone* wants to run the .bit space, whether for its own sake, or to deliberately bring the space namecoin is trying to occupy back under control. I have no real idea how likely that is - but the mere possibility makes .bit less attractive.
|
@electricwings BM-GtyD5exuDJ2kvEbr41XchkC8x9hPxdFd
|
|
|
|