<unnamed>

Public Key

npub18qdwa8rmz4arluryxpppvklcl25kqszdfymv6puu33s2ghz54mvsgxtelw

Profile Code

nprofile1qqsrsxhwn3a3273l7pjrqsskt0u042tqgpx5jdkdq7wgcc9yt322akgprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakq8geunk

Publishing to

relay.snort.social

relay.damus.io

nos.lol

Last Notes

2023-06-07 02:46:38 UTC

- reply

📅 Original date posted:2011-12-14
🗒️ Summary of this message: Invalid URI provided for sending information to David about Bitcoin. Confusion over the appropriate response to a web page suggestion.
📝 Original message:>> "Sure, send it to david.bitcoin.se".>> That's not a valid URI.
I'm not sure I get your point. If someone tells you "hey, check out
the web page at xkcd.com", is that your response or do you just open
up your web browser and type "xkcd.com"?
D.H.

2023-06-07 02:46:31 UTC

- reply

📅 Original date posted:2011-12-14
🗒️ Summary of this message: Use URLs instead of hardcoding specific terms for easier implementation. Example: "send it to david.bitcoin.se".
📝 Original message:> Then forget the hardcoding of "https" the hardcoding of "bitcoin-alias" and> "?handle=" and the original email-looking "genjix at foo.org". Just use the URL.> Then the author of the service can use whatever they want.
I like this a lot. It's very simple to understand and would be very
easy to implement and set up.
"Sure, send it to david.bitcoin.se".
D.H.