<a href="https://www.pepp-pt.org/" rel="nofollow">https://www.pepp-pt.org/</a> and even their manifesto document do not go into the necessary specifics as to how this is planned to be privacy preserving, the manifesto talks about "local trust centers", the article talks about logging BTLE connections. This all seems like stuff we've been discussing in the corresponding HN threads for weeks with no real way to do it in a privacy preserving manner. Without details making these assumptions sounds pretty ridiculous honestly. A bunch of talk about partnering and certifications. If you want to build something to preserve privacy in these scenarios, do it in the open.<p>The other cooperation mentioned there is <a href="https://gesund-zusammen.de/en/" rel="nofollow">https://gesund-zusammen.de/en/</a> - love that their security contact down below is listed as "responsibledisclosure@domain" and they have a bunch of lawyers on the team. How about we rename that to coordinateddisclosure@ folks? And similar to the first initiative, they had time to put up a press package but no technical details on what they actually want to achieve.<p>And all that for techniques that have not been proven to be effective yet? Great.<p>Edit: According to one of their contributors it will be open sourced on GitHub once a stable version is reached. <a href="https://twitter.com/gannimo/status/1245630618462867457" rel="nofollow">https://twitter.com/gannimo/status/1245630618462867457</a> Still not great but at least we'll get a look inside.