{"type":"rich","version":"1.0","author_name":"npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8","author_url":"https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-18\n🗒️ Summary of this message: Jordan Mack agrees with Matt that firstbits is not as desirable as current alias proposals, but sees its usefulness for the \"green address\" case. He questions how saving space is possible by using the whole public key instead of just the address.\n📝 Original message:2011/12/17, Jordan Mack \u003cjordanmack at parhelic.com\u003e:\n\u003e While I think firstbits is an interesting idea, I agree with Matt on\n\u003e this one. Firstbits, while being a clever idea, produces a less\n\u003e desirable solution in comparison to the current alias proposals.\n\nI'm just saying is useful for the \"green address\" particular case.\nPeople don't have to write or memorize the firstbit address, it's just\nto have a shorter string to put it in the QR code. In this particular\ncase you don't really care about \"squatting\" or typographic errors\nbecause the users are bot going to write or even see the firstbit\naddress. I think aliases are a better solution for the \"memorizing use\ncase\".\n\nBut anyway, reading some comments I feel I'm missing something about\nthis proposal. How can you save space by putting the whole public key\ninstead of just the address (a hash of the public key) with each\noutput?\nIs this what it's being proposed?"}