> F-Droid: Repo timestamp expected 1790110069568, but was 1790205675224 IzzyOnDroid F-Droid Repo: Repo timestamp expected 1790100093000, but was 1790272636000
The real problem I think is who should this message go to? My guess is we don't want to have mindless telemetry going from every single user to some central database or repository somewhere. My injection isn't even privacy here. It is that when we have lots of data coming from all over the world, I am afraid someone still has to sift through all this data and make sense of it but we can only understand and prioritize things we already know or are at least able to understand. I feel like this is pulling us in different directions — we want a simpler interface but we also want to expose all sorts of application states that require advanced understanding of how the system works. And someone needs to decide which bucket any particular message goes to — perhaps there is a more opaque but less frightening message like "sync had a hiccup, will retry" or even no message at all surfaces to the user unless it fails multiple consecutive times for the simple, default bucket and more verbose more frequent messages for those who want to see them?
But then even as I write this I can feel like this adds more maintenance headache, even as I push decision making to avoid having to think about a default, I still have to think about a default. The more I think about it, the less sure I am.