Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 02 2018 09:27
    @Arachnid banned @johnny_musk_twitter
  • Aug 18 2018 14:43
    @Arachnid banned @jparicka
  • Jul 24 2018 07:52
    @Arachnid banned @Ether06840759_twitter
  • Jun 06 2018 10:21
    @Arachnid banned @ethsupport1
  • Apr 09 2018 07:24
    @Arachnid banned @JennyJennywren_twitter
Rocky Fikki
@rfikki
So, when do we get started with this feature?
Rabbit
@rabbit
Hello. 馃惏
I've been experimenting with identity contracts, will be focusing on web interoperability, and would be interested in knowing what others are doing. If you're out of the loop too, would be interested in hearing your thoughts / experiments / requirements for anything identity-related. Currently in the middle of moving so I've been too busy but I'll be active here early next week. will be in and out, won't stay long, but will check often.
Rabbit
@rabbit
Disappointed there's been no word in here. If there's a lack of interest, I'll focus on my own efforts.
Viktor Tr贸n
@zelig
Hi all, welcome to namereg world.
Rabbit
@rabbit
Hi 馃憢
Viktor Tr贸n
@zelig
So there is the super primitive initial namereg stack. This will soon be deployed so that all documented frontier features still work.
However this solution is likely temporary.
Gavin and vitalik are working on a namereg we should review and see how it can be used.
And finally there will be swarm. In this context
Rabbit
@rabbit
Is there a repo? It's hard to know which is official / updated.
Viktor Tr贸n
@zelig
For swarm Namereg will need to be proper dns. My primary goal in this group to gather ideas and needs for this. Questions if focus:
  • Mundane matters like current www url character and format restrictions vs non standard requirements. Decide if strict url format is needed
  • hierarchical subdomains and ownership
  • auction system to be used
  • how to handle multiple competing dns /namereg services
If people here are interested to give their 2c let us know
Rabbit
@rabbit
Interested, would now, if not so late. I think a lot about identity so I'll be around.
Rocky Fikki
@rfikki
@zelig, it would help if you provided some guidance and more details as to the current thinking by the internal decision makers with regards to the listed items you mentioned. It would provide a starting point for feedback and discussion.
@zelig is the "super primitive initial namereg stack" you mentioned the one contained within the https://github.com/ethereum/dapp-bin/tree/86c74d6ed825b63909b8cce745545945893599d0
Viktor Tr贸n
@zelig
Hi @rfikki thanks
I wanted to write this all up as you suggest but never got time and thought best to just hop on a channel and not wait forever
Viktor Tr贸n
@zelig
briefly: yes should look around here https://github.com/ethereum/dapp-bin/tree/master/registrar
we got better ideas for auction system for namereg
Viktor Tr贸n
@zelig
i think we would lose on not conforming to url standard because of client libs (routing, parsing, linking).
but i dont like hostname restrictions https://en.wikipedia.org/wiki/Hostname
Rocky Fikki
@rfikki
Another reference for discussion purposes that might be considered is: https://en.wikipedia.org/wiki/Namecoin
Viktor Tr贸n
@zelig
thx :)
Rabbit
@rabbit
@zelig will the namereg address be resolved through a resource registry?
Viktor Tr贸n
@zelig
@rabbit what does this mean?
Rabbit
@rabbit

@zelig resource registry as in anything along the lines of

bytes32 resourceType = sha3("https://ns.ethereum.org/namereg");
registry.resolve(bytes32 resourceType)
registry.resolve(address user, bytes32 resourceType)

where resourceType specifies the contract interface or application context and resolve where a user can override the default.