<oembed><type>rich</type><version>1.0</version><author_name>npub18yq2ukhtlnkuzzykluyjvxap3vtvdqf0arvtag6rx02klk6gymgqp3txp2</author_name><author_url>https://nostr.ae/npub18yq2ukhtlnkuzzykluyjvxap3vtvdqf0arvtag6rx02klk6gymgqp3txp2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2011-12-18&#xA;🗒️ Summary of this message: HTTPS requirement is debatable, but a warning message should be displayed if HTTP is used. JSON is the assumed structure for the answered message format.&#xA;📝 Original message:I can&#39;t speak for Namecoin. As for the HTTPS requirement, I&#39;m on the &#xA;fence. Without it, the resolution is open to a man in the middle attack. &#xA;Perhaps HTTPS should be required, and if HTTP is used, a large warning &#xA;message is displayed.&#xA;&#xA;As for the answered message format, is JSON the assumed structure that &#xA;would be used?&#xA;&#xA;&#xA;On 12/18/2011 1:05 PM, Jorge Timón wrote:&#xA;&gt; If we chose the simple URI proposal namecoin can still be integrated&#xA;&gt; to map the IP of the server by those who want to.&#xA;&gt; Does it removes the necessity of the certificates?&#xA;&gt; If so, we should let people decide between HTTP, HTTPS, namecoin or&#xA;&gt; whatever they trust.&#xA;&gt;&#xA;&gt; Shouldn&#39;t we be also discussing the valid format of the answered&#xA;&gt; message? I mean fields like &#34;amount&#34;, &#34;concept&#34; and such.&#xA;&gt;</html></oembed>