Closed theScrabi closed 4 years ago
I'd like to claim this issue.
All right looking forward for your contribution :)
Keep in mind you will not need any of the stuff that is comunicating with any server (protobuff for example). However leave the gatt part, also maybe crypto.
We still need the protobuf dependency for implementing the Expose Notification API, don't we?
I'll focus on the actual backend part and maybe leave (and deprecate) some bits and pieces that I deem to be helpful later.
The bluetooth advertisement part does not utilize protobuf. I don't know the api that is talking to the app, but I think it does not use protobuf either. Probably the communication with the servers utilize it, but that's not our concern as this is done in the frontend.
As far as I understand from the Exposure Notification API docs we'll receive a list of Protobuf files in the provideDiagnosisKeys()
method, which we'll have to decode on our end.
Ah alight then.
DP-3T apparently also Defines also a protocol to communicate with a server providing the keys of infected people. We don't need this as we only need he bluetooth part. Therefore all the cloud connection parts can be striped from the sdk.