gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] GNS domains


From: Christian Grothoff
Subject: Re: [GNUnet-developers] GNS domains
Date: Mon, 20 Feb 2017 23:53:36 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0

On 02/20/2017 11:14 PM, David Barksdale wrote:
> I'm in favor of anti-squatting measures but I don't like the idea of
> taking money.

Well, as long as you use Taler, that could be also OK. ;-).
In general, I'd like to see various options, that way we can find out
what works.

> Maybe a proof of work and proof of stake (in GNUnet). Like
> you have to compute a proof of work and store it in the zone you're
> registering, and it has to be lookup-able for a couple weeks, before the
> name is finally granted. Any better ideas on how to show you're actually
> contributing resources to GNUnet?

Ah, that's an interesting one.  Maybe just require the zone entry to be
actively maintained (by having the empty label resolve to some valid
record).  That would mean people can't just register, they'd have to at
least participate enough to do DHT PUTs on one record of their zone, and
an entry could expire if it say fails to resolve at all for a period of
6 months (being checked weekly or so).

> Maybe even have a continuing requirement or your name expires. I don't
> see a problem with expiring names, since you don't have much trust with
> the fcfs zone to begin with. If someone is publishing their zone online,
> or on a business card, or in their email signature, they would use the
> .pkey name, not an fcfs name. The fcfs zone is only good for discovering
> zones that may or may not be the one you were looking for, and if you
> become confident it was the one you're looking for you store a record
> for it in your own zone. And if you absolutely must have
> whatever.pin.gnu all you have to do is maintain your zone by updating a
> PoW or something. Any ideas about expiring names?

In general, I think having different zones with different policies makes
most sense. 'pin.gnunet.org' may be for the existing FCFS, and
'live.gnunet.org' may be for the "with valid GNS records in DHT policy",
and 'paid.gnunet.org' for someone who paid for the registration, ...

> 
> On 02/20/2017 03:30 PM, carlo von lynX wrote:
>> The domains do indeed look somewhat neat, but I'm not
>> sceptic regarding first-come-first-served systems that
>> soon become useless if all cool words and brands are
>> squatted.. I think a heuristic what the majority of the
>> social network thinks that "CNN" is would be more
>> accurate in leading people to a pubsub containing CNN
>> content. But if you really want to go for a fcfs way
>> you should at least monetize on it by putting a taler-
>> based price tag on them which is high enough to avoid
>> attracting squatters...
>>
>> If it's for free, somebody will start generating pubkeys
>> for each word in the dictionary...
> 
> 
> 
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnunet-developers
> 

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]