After testing and researching some time, I noticed that the current version of the server is quite buggy, especially regarding errors.
For example, the user can currently crash the server simply by sending an ill-formated UUID string. There has also been a case where there was simply no response returned (Which is also sub-optimal)
For these reasons, I think we should focus even more on handling all possible errors and devise tests (with humans at best) to ensure reliable operation (As already discussed during planning)
It might also be a good idea to revise our zero-log policy in a way that we at least store errors that could not be handled (Without any PII so that there aren't as high standards of security to be upheld)
stephan418
commented
2 years ago
After testing and researching some time, I noticed that the current version of the server is quite buggy, especially regarding errors.
For example, the user can currently crash the server simply by sending an ill-formated UUID string. There has also been a case where there was simply no response returned (Which is also sub-optimal)
For these reasons, I think we should focus even more on handling all possible errors and devise tests (with humans at best) to ensure reliable operation (As already discussed during planning)
It might also be a good idea to revise our zero-log policy in a way that we at least store errors that could not be handled (Without any PII so that there aren't as high standards of security to be upheld)
Request for comments: @Stefan-5422 @Flexla54