Re: peer-to-peer hga@xxxxxx (14 Oct 2019 18:50 UTC)
Re: peer-to-peer Amirouche Boubekki (15 Oct 2019 09:37 UTC)
Re: peer-to-peer hga@xxxxxx (15 Oct 2019 13:41 UTC)
Re: peer-to-peer Amirouche Boubekki (15 Oct 2019 16:56 UTC)
Re: peer-to-peer hga@xxxxxx (15 Oct 2019 18:35 UTC)
Re: peer-to-peer Arne Babenhauserheide (18 Oct 2019 22:32 UTC)
Re: peer-to-peer Amirouche Boubekki (19 Oct 2019 07:22 UTC)
Re: peer-to-peer Arne Babenhauserheide (19 Oct 2019 20:41 UTC)

Re: peer-to-peer Arne Babenhauserheide 19 Oct 2019 20:40 UTC
Amirouche Boubekki <xxxxxx@gmail.com> writes:

> Le sam. 19 oct. 2019 à 00:32, Arne Babenhauserheide <xxxxxx@web.de> a écrit :
>>
>>
>> xxxxxx@ancell-ent.com writes:
>> >> As far as I understand, to be able to offer the features required to
>> >> build (rich internet) applications that are more complex than file
>> >> sharing, one needs to have control over the code of the peer. And
>> >> that is without mentioning some kind of security or network health.
>>
>> I’m not sure whether I understand this correctly. Do you mean that you
>> need control over the other peers or over your local node?
>
> Yes over your local node. To have access to richer datastructures and
> to propagate trust to the network layer you need control of the
> network layer.

Looking at the tools people already built on top of Freenet, which only
gives them an API, I don’t think this is necessarily true.

But it helps to have the possibility to move some implementation from
the client layer to the network layer — this is what for example Freenet
did when site updates via "I’ll just insert to sites with incremented
version number" were turned into USKs (updatable subspace key) that
added date-hints to reach O(1) update detection.

So I agree to some degree :-)

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken