tkuester
Change cot log name when user changes callsign
Currently the cot logs on disk reflect the first name the UID is seen with as far as I can tell, making it difficult to find the right logs some times.
I have an idea on how to resolve this! Instead of using the user's identified callsign / UID (which can change), we could specify the certificate they used to connect with.
That is, if you assign them the certificate JENNY, that's the name of the logfile.
This would also solve a few other issues, such as not knowing which logfile to send data to initially. (Although, obviously, with TCP only this wouldn't work.)
In my case this is semi-public servers, so the same datapackage is used by whoever wants to join, so this approach would not work.
To replicate this scenario you need a user to connect to taky, then change their callsign.
As the user has changed callsign you expect <uid>-<new-callsign>.cot you get <uid>-<old-callsign>.cot.
I suspect fixing this would add overhead to each individual cot read, having to check for callsign and uid every time, so might not be worth it as UID will remain correct, even if callsign is not updated.
The scenarios where this is relevant is when a user is having connection issues and you struggle to find their logs, you can easily just grep for their callsign to figure it out - so any relevant overhead for fixing this is probably not worth it.