Search
crash reports: would you accept anonymous crash reporting if it were disabled by default and you could enable it just when you decide to?
In the Friendica/Mastodon application I am working on, while it was in alpha and beta stage, I have adopted the Sentry SDK for crash reporting, which works very well on Kotlin Multiplatform and is easier to setup than other (closed source, capitalistic and ugly) alternatives.
In doing so, I made an interesting , while I was submitting the app to open source stores (IzzyOnDroid and F-Droid), that if crash reporting is opt-in (i.e. disabled by default but it can be enabled in the app settings) the app is acceptable for their policies because users have to give their consent to enable reports (which are a form of tracking).
Considering there are users complaining about Raccoon for Lemmy crashing (e.g. while creating posts/comments) and that being a "deal breaker" (understandably!), my question is: would you accept it if I included Sentry, making it opt-in? In this way you could enable it just if there is some reproducible issue and turn it off whenever you like (restarting the app is needed to make any change to initialization effective).
Opinions are welcome, I will not do anything unless we decide together, especially because adding this service implies extra work for maintainer(s) 🤣
I am considering to change the default font set, replacing the least used one and introducing a new one for readability
I would like to introduce a new font in the next version, with a particular focus on readability, in order to make the app easier to use.
My choice would be the Atkinson hyperreadable font by the Braille institute, which I personally use in other apps too because it gives my eyes some relief.
However, the APK size of the app increases with every new resource, so instead of just adding a new font I would like to replace the least used of the current ones.
Answer in comments to tell me what you would like to be removed. Thanks as always and #livefasteattrash