Page 1 of 1

Dear squatters!

Posted: Thu Apr 03, 2014 7:31 am
by crosser
It would greatly help if you left some contact information in the `value` field, rather than leaving it an empty string. Otherwise interested parties are left with nothing more than your namecoin address, which is not a good enough way of getting in touch.

Thanks for listening.

In particular, I am interested in d/average:

Code: Select all

{"name":"d/average","value":"","txid":"a986ea1151d612642b7a881a9f7a96f7d0ed9f9aa3751591a67452124cde0dac","address":"My29Kg27PkQLNA8LGcDq4WpB6fa8d7UUQv","expires_in":35856}
average.org is a personal project from which I get no income. I wonder if the current owner would be willing to hand me the d/average name for the cost of transaction.

Incidentally, I was recently working on a project, http://www.average.org/pdns-pipe-nmc/, which may be of interest to namecoin users (but it is not ready for prime time deployment yet.)

Thanks,

Eugene, crosser@average.org, id/crosser

Re: Dear squatters!

Posted: Thu Apr 03, 2014 8:34 am
by MWD
crosser wrote:It would greatly help if you left some contact information in the `value` field, rather than leaving it an empty string.
Agreed.

Re: Dear squatters!

Posted: Mon Sep 22, 2014 7:02 pm
by phelix
You could try to follow the blockchain e.g. at http://namecha.in to see what other domain the owner has registered and whether they have contact information on them or lead you to this info.

I doubt though that the owner will give it away for free.

Re: Dear squatters!

Posted: Wed Sep 24, 2014 7:18 am
by crosser
phelix wrote:You could try to follow the blockchain e.g. at http://namecha.in to see what other domain the owner has registered and whether they have contact information on them or lead you to this info.
I did it back then, but all I found was more "uncontacable" domains.
The owner has renewed them since then, by the way, but did not make it easier to find him/her.

Re: Dear squatters!

Posted: Sat Sep 27, 2014 7:35 am
by biolizard89
crosser wrote:
phelix wrote:You could try to follow the blockchain e.g. at http://namecha.in to see what other domain the owner has registered and whether they have contact information on them or lead you to this info.
I did it back then, but all I found was more "uncontacable" domains.
The owner has renewed them since then, by the way, but did not make it easier to find him/her.
If you're willing to spend a name fee on contacting the name owner, you can register a new name with a message for the owner, and transfer that name to the owner. It will show up in their wallet; maybe they'll notice and read the message. No guarantees that this will work though.

Re: Dear squatters!

Posted: Sat Sep 27, 2014 8:51 pm
by virtual_master
biolizard89 wrote: If you're willing to spend a name fee on contacting the name owner, you can register a new name with a message for the owner, and transfer that name to the owner. It will show up in their wallet; maybe they'll notice and read the message. No guarantees that this will work though.
This is a simple but good idea. But we could make it even better.

1. It would be much easier to use and wouldn't be needed to explain for every user if this would be an automated function from the wallet.
A new menu entry:
-send message-
- enter domain name or another namespace entry
- random name generated(20 character long) and registered it wallet has at least 0.02 NMC
- random name transferred to the name entry holder

The name holder would see the message if he has an open wallet holding that name.

2. The former message would be an open message which could be read by everyone even if not automatically showed in his wallet.
But we could make it encrypted.
What we need for that is a public key from the name holder which could be linked from his name entry in an id/ or another standardized namespace for this purpose.
Actually it could be only a 0.5k length key but it is still better then having a plaintext.

3. We could even make another step of automation to make it easier for user who have difficulties using public key cryptography.
Making another menu entry
- adding encrypted channel-
- select name entry on which to receive encrypted message
- create random keypair(a 0.5k key by the actual size limit)
- storing private key for communication channel in wallet
- publishing public key in the blockchain in a random generated name entry
- and linking the public key from the namespace entry where to receive the messages( for ex id/bob)

If you like the idea we could discuss about it in another thread.

Re: Dear squatters!

Posted: Sun Sep 28, 2014 4:39 am
by biolizard89
virtual_master wrote:
biolizard89 wrote: If you're willing to spend a name fee on contacting the name owner, you can register a new name with a message for the owner, and transfer that name to the owner. It will show up in their wallet; maybe they'll notice and read the message. No guarantees that this will work though.
This is a simple but good idea. But we could make it even better.

1. It would be much easier to use and wouldn't be needed to explain for every user if this would be an automated function from the wallet.
A new menu entry:
-send message-
- enter domain name or another namespace entry
- random name generated(20 character long) and registered it wallet has at least 0.02 NMC
- random name transferred to the name entry holder

The name holder would see the message if he has an open wallet holding that name.

2. The former message would be an open message which could be read by everyone even if not automatically showed in his wallet.
But we could make it encrypted.
What we need for that is a public key from the name holder which could be linked from his name entry in an id/ or another standardized namespace for this purpose.
Actually it could be only a 0.5k length key but it is still better then having a plaintext.

3. We could even make another step of automation to make it easier for user who have difficulties using public key cryptography.
Making another menu entry
- adding encrypted channel-
- select name entry on which to receive encrypted message
- create random keypair(a 0.5k key by the actual size limit)
- storing private key for communication channel in wallet
- publishing public key in the blockchain in a random generated name entry
- and linking the public key from the namespace entry where to receive the messages( for ex id/bob)

If you like the idea we could discuss about it in another thread.
My suggestion was mainly a hack in case someone didn't list contact information. I think a proper solution would just be to list a Bitmessage address when you register a name. No need to clog the blockchain with personal messages, and Bitmessage has much better privacy than a Nakamoto blockchain.