Open Axolord opened 4 years ago
My answer would be "yes because it needs to be adapted to work independently", but I'd like to point out that this is being looked at also by the microG project, which is in use by relatively many people and replicates many parts of the Google Play Services, and the main developer has expressed some interest in adding the exposure notification APIs.
There may still be place for both that and CoraLibre, though: with microG, you normally use apps unchanged, with their official build containing a non-free client library to access Google services, since microG replicates the services. With CoraLibre, the apps would have to be modified and recompiled to use the CoraLibre instead of the Google services, which would be better for FOSS purists, and allow such apps to be included in F-Droid, since otherwise, F-Droid cannot accept apps containing non-free components.
This actually sounds pretty good. Since many corona apps are already open source, compiling with CoraLibre would be pretty easy and the outcoming app would work on AOSP devices, without the need for microG.
How is the development of CoraLibre at the moment? Is the open sourcing of the API from Googles side any help for your Implementation?
Thanks for your explanation!
Alyssa Rosenzweig implemented a Linux implementation of Exposure Notifications functional in Ontario, Canada https://rosenzweig.io/blog/fun-and-games-with-exposure-notifications.html
Since Google just released the source code to their implementation of the Exposure Notification API, is there still a place for CoraLibre?
source: https://github.com/google/exposure-notifications-internals