You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The F-Droid policy doesn't really appreciate sending crash reports without user consent. My opinion/conviction/stallmanism/ideology (choose any @jsackuratens ) makes me think inclusion in F-Droid is important (it's a free software repository of android apps), and we should go back to asking the user for consent when sending crash reports. Objections @vincentadam87@MklBst@jsackuratens ?
Technical note: use full version numbers in tag names when doing releases: 0.25.0 instead of 0.25, that way the F-Droid build scripts can find the proper tags automatically.
The text was updated successfully, but these errors were encountered:
Isn't it already the case that we ask the authorization to send crash reports? I guess that a first agreement, and then an implicit one should be enough
Currently we don't ask for user consent. We could add a popup when the dashboard first opens, asking for agreement, then never ask again (but add a button in the settings).
The text was updated successfully, but these errors were encountered: