Cameron Garnham

@josecelano rebased upon your latest version. :)

> hi @da2ce7 Hello @josecelano > I think we should not include the code we are not going to use and keep only the fastest implementation. We could keep this...

@josecelano I have reimplemented the clock, now it takes the form a Duration, and has Into and From traits implemented for both a local clock, and a fixed clock.

@josecelano and @WarmBeer I'm now felling that my version of the Clock Module is quite rusty: https://github.com/da2ce7/torrust-tracker/blob/protocol-tests/src/protocol/clock.rs What do you think?

Requires rebase upon: #85

I think that the signed invitation should be another TEP. It would depend on [TEP 12](https://github.com/torrust/teps/pull/9).

> I think that the signed invitation should be another TEP. It would depend on [TEP 12](https://github.com/torrust/teps/pull/9). I have been working on this, but haven't published a draft yet.

If you are using the test server data. Then you must enter 'test' . Unfortunately the test server data was generated before we had the password checking code. If you...

When we update the sample / test data. This issue will go away. It is only an issue when migrating old data.

If that works, that is a really good idea. However we still need to trust GitHub...