| 9 Nov 2018 |
 _hc | https://github.com/guardianproject/binary_transparency_log/commit/62211997d6a0fbdad24fa3e3bdde7ff53b26e17c | 08:02:29 |
| _hc | we need to enable that for f-droid.org | 08:03:18 |
| _hc | if you want to take that on as a project, basically, it just needs to be tested to ensure that it doesn't break the normal operations | 08:03:49 |
| _hc | the new gcc136 cfarm box has a full copy of the repo for exactly cases like that, so you can get ssh on that box to work with it | 08:04:31 |
| _hc | distopico (IRC): you can use the fastlane or the fdroid layout in the app. The fdroid layout is here: https://f-droid.org/docs/All_About_Descriptions_Graphics_and_Screenshots/ | 08:07:26 |
 Coffee | In reply to @eighthave:matrix.org
Coffee: have you seen the binary transparency log feature of fdroid repos? It is basically an automated index archive based on git _hc: No, I hadn't seen that. So this just commits consecutive indexes to a git repo? | 08:22:18 |
| Coffee | If we want to do this for index-v1.json, however, we'd probably need to add a reasonable amount of newline to it, or looking over diffs is going to be horrible. | 08:23:38 |
| Coffee | Right now that file has all json in a single line, without even a trailing newline. | 08:24:18 |
| _hc | yeah, click the link, and you'll see nice diffs | 08:41:06 |
| _hc | it pretty-formats the JSON and XML before committing | 08:41:17 |
| _hc | it also includes filesystem changes in a separate JSON file | 08:42:42 |
| Coffee | Looks good. | 08:43:01 |
| _hc | your script is nonetheless useful for repos that don't have that enabled | 08:43:32 |
| Coffee | The advantage of my method is that it preserves signatures. | 08:43:52 |
| _hc | perhaps we can sync up the display of the diffs | 08:43:53 |
| Coffee | I.E. if you rebuild an index jar from diffs, the signature will verify. | 08:44:40 |
| _hc | the signatures are preserved by committing the unmodified signed JAR files | 08:44:41 |
| _hc | I guess we should sync up the file formats then | 08:45:22 |
| Coffee | _hc: can the pretty-formatting be reliably undone to make the signatures verify? | 08:45:52 |
| _hc | I suppose there is a tool to unpretty the XML and JSON, then check it against the signature | 08:46:04 |
| _hc | lol | 08:46:09 |
| Coffee | Heh | 08:46:15 |
| _hc | it is using the pretty-fying from the python libs, so I imagine it should be reversable | 08:46:36 |
| _hc | but I've never tested it | 08:46:44 |
| _hc | or if I have, I've forgotten | 08:46:51 |
| Coffee | I actually thought about putting it in a git repo, but more to get efficient diff compression in the absence of newlines. | 08:50:04 |
 Nico |
<@mathijs:matrix.vgorcum.com> would a letsencrypt cert be desirable?
Nico: any thoughts ^
Mathijs: Yes, Let's Encrypt is fine. That's also what the forum uses. | 08:50:18 |
| Coffee | In the end I wanted individually downloadable bundles though, so you can sync them however. Perhaps by rss feed. | 08:51:05 |
| Coffee | And also with an eye towards possibly implementing it in the client. Do we want to incorporate a git client in it? | 08:53:21 |
| _hc | Coffee: have you seen s#18 and #649 | 09:12:45 |
