There are two ways of doing this in gnunet.
The first is to do it manually, by starting two peers with different
configurations and having them connect.
But the proper way to do testing would be to use the (new) testing API.
Alas, there is no usable documentation for either right now.
BR
Martin
I definitely would like to use and maybe contribute to freenet
Le dim. 15 déc. 2024, 10:54, gogo gogo a écrit :
> Could you either document the second method or can you give me the
> instruction to do it manually please?
>
> Le dim. 15 déc. 2024, 10:43, Martin Schanzenbach
> a écrit :
>
>> Ther
Could you either document the second method or can you give me the
instruction to do it manually please?
Le dim. 15 déc. 2024, 10:43, Martin Schanzenbach
a écrit :
> There are two ways of doing this in gnunet.
> The first is to do it manually, by starting two peers with different
> configuration
It is our goal to have everything documented, of course.
But we cannot force anybody to do anything. We are also not a project
that has the luxury of rejecting contributions left and right for
reasons such as "not documented".
That being said I do share your sentiment. Everything that is crea
I also suggest to add guideline to force dev to test and to make doc on
ANYTHING they create.
What do you all think of this idea please?
Le dim. 15 déc. 2024, 10:58, gogo gogo a écrit :
> I definitely would like to use and maybe contribute to freenet
>
> Le dim. 15 déc. 2024, 10:54, gogo gogo
