Search found 45 matches
- Wed Sep 02, 2015 6:54 am
- Forum: General Discussion
- Topic: Suggestion: Switch to Slack, Gitter, or OSS equivalent
- Replies: 38
- Views: 31877
Re: Suggestion: Switch to Slack, Gitter, or OSS equivalent
I can't see any issues with this.
- Sun Aug 30, 2015 10:41 pm
- Forum: General Discussion
- Topic: Suggestion: Switch to Slack, Gitter, or OSS equivalent
- Replies: 38
- Views: 31877
Re: Suggestion: Switch to Slack, Gitter, or OSS equivalent
I'd rather stay with IRC. While it has usability issues, nobody seems to have invented anything better. An easy way to let people catch up is make log files publically accessible; this is a common practice. Ultimately, any proprietary solution isn't going to be able to compete with the ecosystem of ...
- Sun Jul 12, 2015 12:22 pm
- Forum: Project direction
- Topic: "import" specification
- Replies: 28
- Views: 20821
Re: "import" specification
Yes, I think we're on the same page now. I think anything generating values which understands the semantics of the namespace can do so in a safe fashion, yes. For example, in the case of d/ there are only a finite number of item types, and a GUI, say, is likely to correspond to this. Importantly, 'i...
- Sat Jul 11, 2015 9:20 pm
- Forum: Project direction
- Topic: "import" specification
- Replies: 28
- Views: 20821
Re: "import" specification
At this point you're ignoring half of everything I write. :roll: This is not a response. It is a fact that we can't stop people from creating their own namespaces with their own rules. I have no idea what your position is here. We can't stop people from doing their own thing with their own namespace...
- Fri Jul 10, 2015 7:30 pm
- Forum: Project direction
- Topic: "import" specification
- Replies: 28
- Views: 20821
Re: "import" specification
Firstly, the case for generic import is substantially diminished by the lack of namespaces. Namecoin currently has two official namespaces. We're not facing an excess of namespaces such that a generic import functionality is urgently necessary. There is also u/ (currently using "next" instead of "i...
- Wed Jul 08, 2015 8:07 pm
- Forum: Project direction
- Topic: "import" specification
- Replies: 28
- Views: 20821
Re: "import" specification
So, I see 4 ways to approach the "import subdomain" issue. Have entirely separate import logic per namespace, e.g. implying the traversal of the "map" field. This appears to be what Hugo is suggesting. Have a namespace-specific set of contexts where "import" can appear. Have a namespace-specific na...
- Tue Jun 16, 2015 8:53 pm
- Forum: Project direction
- Topic: Idea: Sidechains for Names
- Replies: 6
- Views: 7954
Re: Idea: Sidechains for Names
example.bit is registered on Namecoin. Control of example.bit is transferred to BitShares by locking the name in Namecoin and posting a DMMS to BitShares. This seems like a very bad idea, as it means the resolvability of a .bit domain is uncertain, and varies base on whether the resolver supports B...
- Mon May 18, 2015 8:22 pm
- Forum: Domain Names / Dot-Bit
- Topic: REQUEST FOR COMMENTS (literally): The d/ specification
- Replies: 13
- Views: 63446
Re: REQUEST FOR COMMENTS (literally): The d/ specification
whooha The JSON object SHOULD be encoded as compactly as possible, without unnecessary whitespace +1 Could you give an example of how a TLS record looks like? IMHO at least for the end user international characters should not be allowed. It makes tricking users way easier. Consequently I vote for d...
- Sat May 16, 2015 8:09 pm
- Forum: Domain Names / Dot-Bit
- Topic: REQUEST FOR COMMENTS (literally): The d/ specification
- Replies: 13
- Views: 63446
REQUEST FOR COMMENTS (literally): The d/ specification
The draft Domain Names specification is now available: https://github.com/hlandau/ncdocs/blob/master/domain-names.md This is a literal request for comments (not an RFC). If you have any questions, comments or issues with the specification, please post them now or forever hold your peace. ;) Overview...
- Thu May 14, 2015 6:41 pm
- Forum: Project direction
- Topic: "import" specification
- Replies: 28
- Views: 20821
Re: "import" specification
The following transcript of a productive discussion regarding import, its genericity, NMControl's handling of it, etc. follows. It should probably be considered recommended reading for anyone working on NMControl. 2015-05-14 17:57:45 @Jeremy_Rand hey hl 2015-05-14 17:57:55 @Jeremy_Rand quick questio...