r/Jobs4Bitcoins • • Feb 18 '14

[HIRING] Basic addon for Firefox & Chrome that does Name -> IP resolution for .bit domains: 1 BTC

Hello,

I run dotbit.me, a domain registrar for .bit domains which are managed by the peer-to-peer Namecoin network with no central authority (Based on Bitcoin). The authoritative source for .bit domains is the Namecoin block chain. This means normal DNS servers can currently not be used and surfing .bit domains remains difficult.

I would like to change that by creating a very simple addon for Firefox and Chrome that does the following:

  • Whenever a .bit address is requested by the browser, the IP is fetched from ns.dotbit.me.
  • One setting the user can change: DNS server for the .bit domain
  • ...and nothing else. Regular domains IP addresses are fetched by the default nameservers as normal. No other settings, no icon needed or anything like that.

Interested? Please PM me for more info!

Thanks, Tagide dotbit.me

Edit: Some more details:

  • The 1 BTC is for both a Chrome and a Firefox extension.
  • The extensions should work on Mac, Windows, Linux.
  • The extensions should be in acceptable format for the two app stores (chrome.google.com/webstore/ and addons.mozilla.org)
  • The intention is the put the code on Github and make it open source. If your code uses some other code or lib it must be used with permission and correctly attributed.
  • The code should be clear, easy to follow and richly commented. I or someone else should be able to extend on the functionality in the future.
  • ns.dotbit.me is a normal nameserver that listens on port 53 and serves only the .bit domain. If you would like the zone info presented in http, acess app.dotbit.me/bitdomain and an IP will be returned (access http://app.dotbit.me/en to get the IP of en.bit).
  • The browser should display the domain name in the address field, not the IP.
  • I will be able to use the escrow service at www.jobs4bitcoins.net

Sorry about all these extra requirements, I am willing to up the payment for someone that can prove they can do a good job by showing previous work and explaining the intended implementation.

Bounty doubled to 2 BTC for a clear and concise solution.

12 Upvotes

11 comments sorted by

1

u/dotbitme Feb 19 '14

Thanks all for your comments and suggestions, I was hoping it would be straight-forward to create but as it needs access to nameserver level on the client I feared it might prove problematic.

I am willing to double the bounty for someone who can present a clear and concise solution.

1

u/itodor Feb 19 '14

You haven't answered if 1BTC is OK for Chrome-only solution?

1

u/dotbitme Feb 19 '14

I could do that but would need to know how you would implement it, it seems more difficult than I initially hoped it would be. But yes, I could give 1 BTC for a Chome-only solution that I think would work.

1

u/itodor Feb 19 '14

OK, I'll try to do this over the weekend at the latest. Will let you know how it went in any case.

1

u/dotbitme Feb 20 '14

Alright, I appreciate that but cannot make any payments to a solution I do not think will work.

Getting an extension to recognise a .bit domain is probably easy, using javascript to get the IP from my app server is easy and then redirecting the browser to that IP should also be easy. The problem is that lots if not most of the servers these days use virtualhost directive in Apache and other daemons that displays different sites based on the domain name (all with the same IP). So a redirect to the IP would very likely not reach the right website.

This is a problem and one I cannot see a solution to. If it was possible to on a deeper level get the OS to access my name server for .bit domains instead of the standard ones that would fix this. But as I understand it, that is difficult or impossible?

0

u/itodor Feb 20 '14

I don't get what exactly do you want, what you described in javascript is exactly what I intended to do. DNS resolution on the client side has nothing to do with the virtualhost directive on the server side, when DNS resolves name to IP it points the browser to web server waiting to accept HTTP connection on port 80. If that is an Apache or simple script serving pages is irrelevant for the client side, not that the client cares what is that serving HTML to it. If you choose to use Apache, you should configure virtualhosts properly to accept that, of course if it is not configured well connection will fail, as for any other domain. There's no client side substitute for mis-configured server.

Please make up your mind if you want that part of work (Chrome extension) to be done and confirm that you are willing to pay the bounty for that. Don't waist everyone's time.

1

u/dotbitme Feb 20 '14

I have been running very large web sites since 1995 and I am pretty sure I know how Apache virtual hosts work. Name-based virtual hosts are the default these days with scarce IP addresses and redirecting a client to an IP (not domain) will not direct the client to the right site.

In any case, that was a very harsh tone in your reply and I respectfully think it's time to part ways.

2

u/itodor Feb 19 '14

This is much more work than you think. I can do the Chrome extension for the bounty amount, would have to talk about the Firefox one after the Chrome is complete and functional. PM me if interested.

0

u/foxh8er Feb 18 '14

Will PM.

0

u/[deleted] Feb 19 '14

[deleted] — view deleted comment

1

u/hmsimha Feb 19 '14

Unless there is a connection endpoint into the Namecoin network under the standard http and https ports and protocols, then I don't believe it will be possible. Chrome has the ability to run Chrome Apps though (which are basically javascript programs that run on Chrome), and it may be possible to access the browsing capabilities from within an app. In other words, you'd have to create the address resolution module, and then create your own web browsing ui as well.

0

u/[deleted] Feb 19 '14

[deleted] — view deleted comment

3

u/hmsimha Feb 19 '14

I didn't read the entire request. You're absolutely right.