Jesse V:
> On 09/27/2016 10:05 AM, Jeremy Rand wrote:
>> Namecoin also can be used for name-level load balancing, although I
>> haven't really carefully considered the anonymity effects of the load
>> balancing (e.g. does it open the risk of fingerprinting?), so that
>> feature is lower priority un
On 09/27/2016 10:05 AM, Jeremy Rand wrote:
> Namecoin also can be used for name-level load balancing, although I
> haven't really carefully considered the anonymity effects of the load
> balancing (e.g. does it open the risk of fingerprinting?), so that
> feature is lower priority until I can think
Hi tor-dev@,
Ivan Markin:
> IMO an onion service should publish its first descriptor instantly. If
> something happens afterwards and one has to fix the descriptor - deal
> with it with backoff/delay to prevent DoS on HSDirs.
> I think that most of the ephemeral services are not going to use more
I'll add a note on GNS to your wiki George, but..
On Sat, 2016-08-20 at 16:48 +0300, George Kadianakis wrote:
> We really need to start serious work in this area ASAP! Maybe let's
> start by
> making a wiki page that lists the various potential solutions (GNS,
> Namecoin,
> Blockstack, OnioNS, et
Jesse V:
> On 09/27/2016 02:27 AM, Jeremy Rand wrote:
>> Hello! I just had a chance to look through the latest state of the wiki
>> page (thanks to everyone who's been expanding it). I've added several
>> items to the security properties and drawbacks sections of Namecoin, and
>> made a few trivi
Jesse V:
> On 09/27/2016 02:39 AM, Jeremy Rand wrote:
>> Relatedly -- I had some trouble summarizing some of the items in the
>> Namecoin section because the security, privacy, and scalability
>> properties of Namecoin are somewhat different depending on whether the
>> user is using a full node (do
On 09/27/2016 02:27 AM, Jeremy Rand wrote:
> Hello! I just had a chance to look through the latest state of the wiki
> page (thanks to everyone who's been expanding it). I've added several
> items to the security properties and drawbacks sections of Namecoin, and
> made a few trivial corrections;
On 09/27/2016 02:39 AM, Jeremy Rand wrote:
> Relatedly -- I had some trouble summarizing some of the items in the
> Namecoin section because the security, privacy, and scalability
> properties of Namecoin are somewhat different depending on whether the
> user is using a full node (downloads the ent
