| 6 Jul 2021 |
 Abel | I don't think they are necessarily trying to make a quick buck by throwing audacity under the bus. Muse Group has a massively successful other open source application: Muse Score | 14:04:08 |
| Abel | a program for composers to compose sheet music | 14:04:19 |
| Abel | muse score 3 is gpl v2, and has telemetry and so forth in it already | 14:05:10 |
| Abel | from their mind I think they're just trying to apply their internal process to audacity. | 14:05:28 |
| Abel | But they didn't realize that while Muse Score is a super niche program used by nerdy music composers, Audacity is a high profile foss program used by nerdy FOSS advocates | 14:06:09 |
| Abel | music composers aren't really up in arms about privacy policies and telemtry | 14:06:39 |
 threeletteracronym | I see. Makes sense. | 14:06:52 |
 gina_h | I get the sense people are just waiting to see which fork will be "the one" for everybody to adopt instead | 14:25:15 |
| 7 Jul 2021 |
 n8fr8 | gina_h: https://gitlab.com/cleaninsights/cleaninsights-implementations/-/issues | 15:23:57 |
| 21 Jul 2021 |
| n8fr8 | https://gitlab.com/cleaninsights/cleaninsights-implementations/-/issues | 15:20:05 |
| gina_h | do we have an FAQ for Clean Insights already? | 19:00:40 |
| n8fr8 | No. We are working on this "getting started" page content, and a FAQ as well could be put into that effort. | 19:02:07 |
| gina_h | Gotcha. LMK if I can pitch in. | 19:02:15 |
| n8fr8 | this is the start we have made to that page: https://docs.google.com/document/d/12Varg7JREUO0slcetMaUW-8wva8fAPKr55t9WhD9VjA/edit?usp=sharing | 19:03:26 |
| n8fr8 | i'll think about how best to organze/host an FAQ. I suppose just as markdown to start in our specifications repo, and then we can integrate that into the website build process. | 19:03:47 |
| 22 Jul 2021 |
| n8fr8 | interesting project from Google: https://fuchsia.googlesource.com/cobalt | 17:13:15 |
| n8fr8 | Cobalt is a pipeline for collecting metrics data from user-owned devices in the field and producing aggregated reports.
Cobalt includes a suite of features for preserving user privacy and anonymity while giving product owners the data they need to improve their products. | 17:13:28 |
| gina_h | Interesting. How similar/different is it to CI? | 18:33:38 |
| n8fr8 | not sure yet! | 19:12:01 |
| 28 Jul 2021 |
| gina_h | Any chance y'all can use some of your coffee $ to fund a logo design for Clean Insights? | 21:51:01 |
| gina_h | If not, I can see if I can find some funds in BASICS to support it | 21:51:21 |
| threeletteracronym | Yay for logo! | 21:58:29 |
| n8fr8 | Yes it's happening. The coffee logo label design is part of it. | 22:41:32 |
| n8fr8 | Thanks for the offer tho! | 22:41:42 |
| 3 Aug 2021 |
| gina_h | crwinfrey: I wonder if we might incorporate this Rapid Risk Assessment from Mozilla when tool teams are assessing risk around their user data https://infosec.mozilla.org/guidelines/risk/rapid_risk_assessment.html | 17:16:30 |
| 9 Aug 2021 |
| n8fr8 | some interesting working from stanford, that seems to be getting OTF funding | 14:54:08 |
| n8fr8 | https://crypto.stanford.edu/prio/ | 14:54:09 |
| n8fr8 | https://www.abetterinternet.org/prio/ | 14:54:13 |
| n8fr8 | though a much more multiparty compute / cryptographic approach | 14:55:13 |
| 11 Aug 2021 |
 _hc | looks like Google is following the model laid out in Clean Insights:
"No ad-hoc, post-facto querying. Whereas on other telemetry systems standard practice is to “collect now; ask questions later”, with Cobalt the analyst must think in advance about what aggregations they wish to report and predeclare reports." | 09:30:42 |
