<oembed><type>rich</type><version>1.0</version><author_name>npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_name><author_url>https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2011-12-14&#xA;🗒️ Summary of this message: A suggestion was made to simplify the use of a URL instead of hardcoding specific elements, but the example given was not a valid URI.&#xA;📝 Original message:On Wednesday, December 14, 2011 2:22:12 PM D.H. wrote:&#xA;&gt; &gt; Then forget the hardcoding of &#34;https&#34; the hardcoding of &#34;bitcoin-alias&#34;&#xA;&gt; &gt; and&gt; &#34;?handle=&#34; and the original email-looking &#34;genjix at foo.org&#34;.  Just&#xA;&gt; &gt; use the URL.&gt; Then the author of the service can use whatever they want.&#xA;&gt; &#xA;&gt; I like this a lot. It&#39;s very simple to understand and would be very&#xA;&gt; easy to implement and set up.&#xA;&gt; &#xA;&gt; &#34;Sure, send it to david.bitcoin.se&#34;.&#xA;&#xA;That&#39;s not a valid URI.</html></oembed>