Mick van Dijke

I haven't looked into this yet, but I noticed that most rust projects have a https://crates.io/ page, so it would probably be great for our project too :)

I'm not sure what the best practice is in this case. But I do prefer keeping the old tags and version numbers as they are and continue on a new...

> Given we only use the port, I suppose it will generate the same ID for all clients using the same port during the same hour. That should not be...

I've edited my reply to also include the peer port.

https://github.com/torrust/torrust-tracker/pull/67

It is only possible to manually add existing tracker keys directly to the database and they have to be 32 chars.

Hey! I'm terribly sorry for the late response. I've completely read over your issue. I believe the mistake is made in `[http_trackers]` and `[udp_trackers]`. Both should have double brackets: `[[http_trackers]]`...

I think you're right, this should be returning a 401.

Thank you for the heads-up. I've implemented a fix for this in the coming release: https://github.com/torrust/torrust-tracker/commit/aac9ac72bdd300ffb2959ba6f2a1ee04ecac5895

1# No this was a fix for HTTP only, I'm looking into UDP atm. 2# The peer_timeout variable is the max amount of seconds a peer may be inactive (after...