4 ms·
> Thanks for that I'll have a read. > Is there any discussion about other countries using this NHS app (the repo says MIT license)? > Each country could custo
by g_p 6y ago
> Thanks for that I'll have a read.
> Is there any discussion about other countries using this NHS app (the repo says MIT license)?
> Each country could customise the alert heuristic but it seems like a waste of resources for each country to code their own app for a global problem.
Not seen any other country talking about this yet although it only came out today in source form, and still is technically in limited beta. I imagine Australia and Singapore will be interested in the iOS Bluetooth in sleep workaround method, as that does appear to be novel and not really done before.
If you implement the same basic API, it would be easy for another country to implement. The nice aspect of this design is that you can have an MVP (like UK has right now) while you evolve the more complex heuristics and models on the backend, and add those as you develop them. I'd agree it's a waste to build multiple apps, and I imagine countries will be looking at this approach now, and the value of an app with real working code, versus trying to build something.
The Bluetooth protocol itself is designed to support multiple countries using it - the outer message contains a country code flag so you know which country's health system you'd need to communicate with in order to exchange info of a proximity event.
- seanwilson 6y ago> the iOS Bluetooth in sleep workaround method Why do they need to find a workaround? Can't Apple tell them the best way or push an iOS patch to help?
- g_p 6y ago> > the iOS Bluetooth in sleep workaround method > Why do they need to find a workaround? Can't Apple tell them the best way or push an iOS patch to help? Apple seem to take the view governments should use their decentralised approach, or not do it, and don't seem to have been willing to help governments do this without using their "joint approach" with Google. I am normally the first to back anything decentralised. But in this case, the stated goals of the app (from a very good NCSC writeup I've linked elsewhere in these comments) simply don't work with a decentralised approach (namely being able to do risk-from calculation, not just risk-to, and being able to gather and model from symptoms whether others should keep isolating or can go back to normal). Given Apple said it wouldn't help anyone not wanting to go "their" way, it's quite reassuring to see that engineers do what they do best, finding a new workaround, and making details of it available for any other devs... Perhaps Australia can use this in their app now to fix their issues with Bluetooth and iOS.