{"type":"rich","version":"1.0","author_name":"npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","author_url":"https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-14\n🗒️ 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.\n📝 Original message:On Wednesday, December 14, 2011 2:22:12 PM D.H. wrote:\n\u003e \u003e Then forget the hardcoding of \"https\" the hardcoding of \"bitcoin-alias\"\n\u003e \u003e and\u003e \"?handle=\" and the original email-looking \"genjix at foo.org\".  Just\n\u003e \u003e use the URL.\u003e Then the author of the service can use whatever they want.\n\u003e \n\u003e I like this a lot. It's very simple to understand and would be very\n\u003e easy to implement and set up.\n\u003e \n\u003e \"Sure, send it to david.bitcoin.se\".\n\nThat's not a valid URI."}