Jorge Timón [ARCHIVE] on Nostr: 📅 Original date posted:2011-12-12 🗒️ Summary of this message: The discussion ...
📅 Original date posted:2011-12-12
🗒️ Summary of this message: The discussion is about using different hosts or reserving a string in Namecoin to solve the problem of having a unique identifier.
📝 Original message:Is the point is to have different hosts like in jtimon at gmail.com,
jtimon at timon.es, etc. so if jtimon is already taken I can take another
host?
What about reserving directly the string "jtimon at nottaken.org" or
"jtimon::public::receiving::bitcoin" in namecoin?
I'm confused about the problem we're trying to solve.
2011/12/13, Luke-Jr <luke at dashjr.org>:
> On Monday, December 12, 2011 6:37:56 PM Jorge Timón wrote:
>> Would it be too strange to use namecoin?
>
> This has the same problem as FirstBits, except .bit domains are dirt cheap,
> whereas vanitygen at least slows down grabbing all the common words...
>
🗒️ Summary of this message: The discussion is about using different hosts or reserving a string in Namecoin to solve the problem of having a unique identifier.
📝 Original message:Is the point is to have different hosts like in jtimon at gmail.com,
jtimon at timon.es, etc. so if jtimon is already taken I can take another
host?
What about reserving directly the string "jtimon at nottaken.org" or
"jtimon::public::receiving::bitcoin" in namecoin?
I'm confused about the problem we're trying to solve.
2011/12/13, Luke-Jr <luke at dashjr.org>:
> On Monday, December 12, 2011 6:37:56 PM Jorge Timón wrote:
>> Would it be too strange to use namecoin?
>
> This has the same problem as FirstBits, except .bit domains are dirt cheap,
> whereas vanitygen at least slows down grabbing all the common words...
>