Thank you. Whenever users can’t receive messages I can’t think of anything until it’s fixed. The team feels this pain too. We do try to fix issue as soon as possible, and in general last week incident we see as not acceptable even for beta releases, leave alone production. So we’re improving the test coverage now, and we will prioritise delivery receipts for 5.2 or 5.3 - that would reduce users’ and our stress a lot.
The cadence of f-droid is indeed a pain, there are two problems:
1) the time it takes to build the app. Because there is no Nix cache that holds GHC cross compiler and the stack it has to be compiled every time we build the app - it takes ~12 hours. On our CI the build takes either 20-60 min, depending on the scope of changes. We need to figure out how to use Nix cache, but the problem is that it’s not a priority when exactly two apps in f-droid use Nix…
2) the time it takes to update the whole F-Droid repo - I don’t fully understand the design, so not sure if it can be improved to have f-droid updated per app…
Users can of course switch to another source, but the app would be signed with another key (as it’s not a solved problem doing reproducible builds with GHC), which means they would have to export db, reinstall the app, and import again.
I don’t have a simple solution here…
simplex / SimpleX Chat
npub1exv…d828
2023-05-30 01:02:49
in reply to nevent1q…vl30
Author Public Key
npub1exv22uulqnmlluszc4yk92jhs2e5ajcs6mu3t00a6avzjcalj9csm7d828Published at
2023-05-30 01:02:49Event JSON
{
"id": "404127c67505c1832f960dc7d43a311704fa78ac346d84d33e1a38056820ef0a",
"pubkey": "c998a5739f04f7fff202c54962aa5782b34ecb10d6f915bdfdd7582963bf9171",
"created_at": 1685401369,
"kind": 1,
"tags": [
[
"e",
"4057d1011f4b5491d575eab5e2fec6348205c1cede16ea3a13b73ff6cc13cf3a"
],
[
"e",
"45d520e2fb4473a1719e45dd912cfb5b3facf655152a84e24051c8575b7dd46b"
],
[
"p",
"e78b0286e720e1024c392f393f1638154bbf47af8870bcb5743002ced2c7a71f"
]
],
"content": "Thank you. Whenever users can’t receive messages I can’t think of anything until it’s fixed. The team feels this pain too. We do try to fix issue as soon as possible, and in general last week incident we see as not acceptable even for beta releases, leave alone production. So we’re improving the test coverage now, and we will prioritise delivery receipts for 5.2 or 5.3 - that would reduce users’ and our stress a lot.\n\nThe cadence of f-droid is indeed a pain, there are two problems:\n\n1) the time it takes to build the app. Because there is no Nix cache that holds GHC cross compiler and the stack it has to be compiled every time we build the app - it takes ~12 hours. On our CI the build takes either 20-60 min, depending on the scope of changes. We need to figure out how to use Nix cache, but the problem is that it’s not a priority when exactly two apps in f-droid use Nix…\n\n2) the time it takes to update the whole F-Droid repo - I don’t fully understand the design, so not sure if it can be improved to have f-droid updated per app…\n\nUsers can of course switch to another source, but the app would be signed with another key (as it’s not a solved problem doing reproducible builds with GHC), which means they would have to export db, reinstall the app, and import again.\n\nI don’t have a simple solution here…",
"sig": "2f9cd71d59c6647f2d8b8a5ae9aba836f8f422d70b40753387b052ae3e9e854c0c0aab9bd033b6b4d50a21f94df369f05fc1cdc6008b10dd5ca15f7c99c32c1f"
}