Jose Celano

Ok, I understand now. It's more important to keep a list of real peers rather than avoiding having wrong info for a peer. Thank you @WarmBeer, I think you should...

> @josecelano is it ok to merge? No, not yet. I've moved the pending tasks from the comment to the [PR description](https://github.com/torrust/torrust-tracker/pull/60#issue-1334659314).

> @WarmBeer > > > Over this [having the extra step of producing the Time_Bound_Pepper] > > Of course you are right. It is just the same. I separated the...

hi @WarmBeer I have to generate the `SERVER_SECRET` when the UDP tracker starts. Should all jobs use the same secret? If yes, I suppose it would be something like this:...

hi @da2ce7 cool! Questions: - In your initial proposal, you also use a hash. Is there any reason you are not using it? Pros: - Precision is better. Since we...

@da2ce7, @WarmBeer and I are considering doing a benchmarking for memory consumption. We have the feeling that @WarmBeer's first implementation (using hash) would consume much less memory, and that could...

> hi @WarmBeer I have to generate the `SERVER_SECRET` when the UDP tracker starts. Should all jobs use the same secret? If yes, I suppose it would be something like...

I've created a PR with a Dockerfile only for this service. We could create docker images also for the backend and frontend. I think it would be also helpful to...

> Hi @josecelano - take a look at https://github.com/zorlin/torrust-docker ... > > :) Hi @Zorlin cool!!! Just a couple of questions/comments: 1. I think it would be nice to have...

I've created the summary below with the current state. I think it's useful to define first what we have before proposing new changes. I called the "UNVERIFIED" user "AUTHENTICATED" and...