Investigate self-hosted crash reporting
Motivation
Our F-Droid builds do not include any sort of crash reporting or analytics. The reason for this is that the open source community, and F-Droid users in particular, do not want their data being sent to a big data miner like Google.
OTOH, we are less able to debug issues for these users because we have less (read: zero) visibility into their crashes.
So it would be nice if we could set up some sort of self-hosted / de-Googled crash reporting.
Plan of action
@taras.smakula investigated the space of what's available, and it appears that the best open source, self hosted option is ACRA. ACRA has an open source server called Acrarium.
I (@cvwright) tried to set up Acrarium on our servers earlier this summer. Unfortunately that effort was a complete fail.
However, we now know that the version of Fedora that we were running at the time had a strange kernel bug. For whatever reason, it broke JVM-based applications. (It also broke ma1sd; this is why we migrated away from Fedora.)
So, now I need to try again with Acrarium on our new Rocky Linux servers.