| 12 Nov 2018 |
 _hc | fdroid4imbig73ep.onion is kind of funny | 11:23:29 |
| _hc | still no fdroidorg...onoin | 11:31:08 |
| _hc | here's a list of what exists so far https://clbin.com/3SLbl | 11:34:42 |
 Mathijs | In reply to @eighthave:matrix.org
Nico: Mathijs running jitsi is as complicated as matrix, so I say let's first see how it goes with matrix before also trying to run jitsi Agreed | 11:48:00 |
| Mathijs | I have never tried running jitsi myself | 11:48:11 |
 @bubuiic:matrix.org |
fdroidorb
close :)
| 12:00:04 |
| Mathijs | I want an fdroid orb | 12:00:59 |
|  etue left the room. | 12:01:13 |
| _hc | lol, we were just offered two more giant servers | 12:18:12 |
| Mathijs | That can't be a bad thing | 12:39:04 |
| Mathijs | out of curiosity, is there any contingency for the small bus factor of f-droid? | 12:44:35 |
| _hc | how so? | 13:27:32 |
| Mathijs | well, from what I understood, ciaran is the only one with the signing keys, right? | 13:54:59 |
| _hc | yup, that's a tough one | 14:01:28 |
| _hc | we've made a lot of progress though | 14:01:35 |
| _hc | with bus-factor in general | 14:01:51 |
| Mathijs | It's not like I'm advocating him spreading the signing keys around like candy | 14:01:56 |
| Mathijs | but having some kind of fail-safe seems like a good idea | 14:02:12 |
| _hc | like the whole buildserver/publishing setup is almost put into the automation, mostly created by uniq | 14:02:15 |
|  Tovok7 joined the room. | 14:02:30 |
| Mathijs | yeah, I noticed there's a lot of progress | 14:02:52 |
| Tovok7 | we'd probably release a new repo alongside the old one, publish a new client version including it and ask *all* of our users to upgrade manually to the new client (that probably also has a new signing key). | 14:02:31 |
| _hc | everyone agrees there should be improvements... | 14:02:34 |
| _hc | hi Tovok7 ! | 14:03:03 |
| Tovok7 | o/ | 14:03:10 |
| Mathijs | I obviously started thinking about it due to the dns records taking a while | 14:03:25 |
| Mathijs | In reply to @freenode_Tovok7:matrix.org
we'd probably release a new repo alongside the old one, publish a new client version including it and ask *all* of our users to upgrade manually to the new client (that probably also has a new signing key). that is probably the best solution at this point, but also a major drag for all users | 14:03:58 |
| Tovok7 | I brainstormed about a new decentralized repo some time back. | 14:04:04 |
| Mathijs | the whole ipfs mirror is a decent idea in that sense | 14:04:57 |
| Mathijs | I'm not sure what the ideal solution in general would be, though | 14:05:39 |
