Storing .bit starting webpage as namespace entry
Re: Storing .bit starting webpage as namespace entry
Most people believed the "translate" option from the spec was doing this... and were asking for this feature after.
NamecoinID: id/khal
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T
Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T
Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: Storing .bit starting webpage as namespace entry
Yep. One feature which I plan to add in the future to FreeSpeechMe is a full HTTP parser which can change headers, which will give the capabilities described in this thread.phelix wrote:I have a feeling we are getting a little closer to this with FreeSpeechMe (new Convergence Firefox plugin).phelix wrote:This is a great idea.biolizard89 wrote:I was thinking about something similar: add an "http" field, which compliant implementations should display as an HTML iframe, an HTTP redirect, or otherwise load the HTTP URL specified by the value of the "http" field. The value would be used as a "base" URL; i.e. I could specify this:
name: d/myforum
value: { "http" : "http://www.mysite.com/forum"}
Visiting http://www.myforum.bit/1234 would take me to http://www.mysite.com/forum/1234
This scheme might need modification to handle multiple resolvers (e.g. the implementation should be able to choose a generic TLD, .onion TLD, .i2p TLD, etc. based on user choice), but I think that's easy enough.
I think this would meet the main use case of your proposal, without using as much storage in the blockchain, and would also prevent idiots from shoving Javascript malware in the blockchain or whatever other bad things might happen from embedding arbitrary web pages in the blockchain.
Another benefit of this way of doing it is that (I think, haven't tested) proxy-based implementations like Convergence should be able to transparently translate the HTTP headers such that the URL bar still works as normal; i.e. the browser thinks it's actually visiting the correct .bit page even if you click links, but the server receives the headers requesting a .com page.
supersite.bit --> http://supersite.somefreewebspacehoster.com location bar: supersite.bit
supersite.bit/products --> http://supersite.somefreewebspacehoster.com/products location bar: supersite.bit/products
Cheap domain names with SSL and TLS for everybody!
-
- Posts: 801
- Joined: Sun Aug 18, 2013 8:26 pm
- os: mac
Re: Storing .bit starting webpage as namespace entry
Duplicate work: http://forum.namecoin.info/viewtopic.php?f=5&t=1658
Looks like I need to spend more time on the forum! Someone shoulder-tap me next time frame resolution comes up
Let's do it!
Looks like I need to spend more time on the forum! Someone shoulder-tap me next time frame resolution comes up
Let's do it!
DNS is much more than a key->value datastore.
-
- Posts: 801
- Joined: Sun Aug 18, 2013 8:26 pm
- os: mac
Re: Storing .bit starting webpage as namespace entry
I wrote an initial spec here.
Jeremy, you should write something up regarding your encryption indication proposal (which encryption key is applied where).
Jeremy, you should write something up regarding your encryption indication proposal (which encryption key is applied where).
DNS is much more than a key->value datastore.