Uh oh!
There was an error while loading. Please reload this page.
Rename Merkle links key from mlink to link - #64
Conversation
jbenet
commented
Jan 22, 2016
this LGTM. though do we want |
mildred
commented
Jan 22, 2016
I didn't understand what you said about |
jbenet
commented
Jan 24, 2016
Sorry, let me rephrase: do we want (i myself am leaning towards directives + escaping) |
mildred
commented
Jan 25, 2016
If you want to add escaping, we can either let the application do the escaping on their own, or handle the escaping ourselves. Escaping implies that we will be able to provide the application with either the escaped (original) version, or the unescaped (with link information removed) objects. If the application wants to look at links, it will not be able to do so in the unescaped version the I'd be tempted to say it doesn't matter if the application create links unknowingly. We'll just never use them. So let's use If we want to provide an easy way to avoid that, just use |
jbenet
commented
Jan 25, 2016
Very well thought out. thanks
Yep totally agreed here, i think this ^ is the right choice. |
Rename Merkle links key from mlink to link
jbenet
commented
Feb 11, 2016
thanks @mildred |
Merges to #37
Replaces
mlinkoccurrences withlinkwith a paragraph to explain how merkle-links are formed. Original comment and follow up